mizcausevic-dev/agent-card-tool-coverage

MCPcommunity
mizcausevic-devAGPL-3.0Updated 3mo 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 →
3mo agoLast update
Package
Authormizcausevic-dev
LicenseAGPL-3.0
Sourcegithub
GitHubmizcausevic-dev/agent-card-tool-coverage
SBOMCycloneDX 1.6 ↓
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 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

1 tool · none privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

secret-debug-toolNo description published

This tool published no description. Forge does not invent one.

0 of 1 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.

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
Alternatives
Comparing tool surfaces…

Tools exposed

1 tool · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

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.