mizcausevic-dev/agent-card-tool-coverage

MCPcommunity
mizcausevic-devAGPL-3.0Updated 2mo agoGitHub

Conformance check between an A2A AgentCard's declared tools and an MCP server's tools/list. Reports missing (declared but not exposed), undeclared (exposed but not in card), matched; counts by side-effect class. Library + CLI.

Conformance check between an A2A AgentCard and an MCP server's . Answers: does the agent's declared tool surface match what the server actually exposes? Status: v0.1.0 — Node 20/22 supported, library + CLI. The AgentCard declares what tools the agent says it uses. The MCP server's declares what's actually available. These two surfaces tend to drift: a tool gets added on the server before the card…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2mo agoLast update
Package
Authormizcausevic-dev
LicenseAGPL-3.0
Sourcegithub
GitHubmizcausevic-dev/agent-card-tool-coverage
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface1 tool · none privileged
Security scan✓ CleanvHEAD · 2mo ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Conformance check between an A2A AgentCard and an MCP server's . Answers: does the agent's declared tool surface match what the server actually exposes? Status: v0.1.0 — Node 20/22 supported, library + CLI. The AgentCard declares what tools the agent says it uses. The MCP server's declares what's actually available. These two surfaces tend to drift: a tool gets added on the server before the card is updated, or a tool is removed from the server but still listed in the card. Either drift breaks…

Keywords
a2aagent-cardsai-governanceconformancegovernancemcptypescript