Read AFMR failure modes and discover scoped attestation and lift-evidence contracts.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://afmr.ai/mcp4 tools · 189mshttps://afmr.ai/api/rpc4 tools · 92msdiscover_afmrReturn canonical AFMR specifications, registries, schemas, endpoints, and scope boundaries.Return canonical AFMR specifications, registries, schemas, endpoints, and scope boundaries.
No input schema was published for this tool.
lookup_failure_modeFind exact AFMR 1.0 failure-mode records by permanent ID or bounded text query.Find exact AFMR 1.0 failure-mode records by permanent ID or bounded text query.
| Parameter | Type | Description |
|---|---|---|
| id | string | Exact permanent family identifier, for example AFMR-F010. |
| query | string | Text matched against ID, name, definition, and class. |
| limit | integer | — |
get_reputation_attestation_contractReturn the portable attestation, trust-profile, verifier-result, endpoint-registry, and lifecycle contracts.Return the portable attestation, trust-profile, verifier-result, endpoint-registry, and lifecycle contracts.
No input schema was published for this tool.
get_lift_evidence_contractReturn the stable configuration-scoped public-card schema and empty public index; no results are asserted.Return the stable configuration-scoped public-card schema and empty public index; no results are asserted.
No input schema was published for this tool.
4 of 4 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Read AFMR failure modes and discover scoped attestation and lift-evidence contracts.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.