# AFMR Discovery [Health: Active]

**Category:** ⚖️ Legal  
**Repository:** https://afmr.ai/  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/afmr-discovery

## Description
Read AFMR failure modes and discover scoped attestation and lift-evidence contracts.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What the AFMR Discovery MCP server does

The AFMR Discovery MCP server is described as a way to read AFMR failure modes and discover two kinds of scoped contracts: attestation contracts and lift-evidence contracts. Its purpose is therefore focused on AFMR discovery rather than broad legal research, document management, or general-purpose data access.

The available description does not define a larger set of operations, supported data formats, authentication methods, or output schemas. Treat the documented scope as limited to failure-mode reading and contract discovery until the provider supplies more technical details.

## How it works

An AI agent uses the MCP server to request information from the AFMR system or service. The stated workflow has two parts:

- Read AFMR failure modes.
- Discover scoped attestation and lift-evidence contracts.

The material also does not specify whether discovery supports keywords, identifiers, structured filters, pagination, or other query options.

The AFMR Discovery MCP server should be evaluated against the agent workflow you need. It may fit a process that must inspect AFMR failure modes or locate relevant evidence-related contracts. The available information is not enough to confirm behavior for writing, updating, validating, or executing contracts.

## Limitations and notes

No README is available for this listing.

The listing does not identify specific desktop clients or development environments. It also does not state whether the service is hosted, run locally, accessed over HTTP, or launched through standard input and output. Do not assume a particular connection method without provider documentation.

The description refers to AFMR failure modes, scoped attestation contracts, and lift-evidence contracts, but it does not define those concepts in detail. Developers should confirm the terminology, expected inputs, result structure, access controls, and handling of sensitive information before incorporating the AFMR Discovery MCP server into an automated workflow.

For implementation planning, the safest confirmed expectation is narrow: an MCP-based interface for reading AFMR failure modes and discovering the two named contract categories. All additional operational behavior remains unspecified by the supplied source.

_Full upstream README: https://allmcps.com/mcp/afmr-discovery/readme_