com.resolvemesh/compatibility

MCPcommunitylive
v0.1.0com.resolvemeshUnknownUpdated 2mo ago

Read-only, source-backed compatibility lookups and approved changes for ResolveMesh's catalog.

Endpoint healthlive
checked 2 days ago · 201ms
100% of the last 6 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

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.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2mo agoLast update
Package
Authorcom.resolvemesh
LicenseUnknown
Version0.1.0
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: this listing has no repository on file, so `forge publish` cannot verify ownership automatically. Use "Claim this listing" above — Forge reviews these by hand.
—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
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface2 tools · none privileged
Security scan✓ Cleanvlive · 23d agoHow well does this scan work?
EvalsNone
IndexedJul 14, 2026

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

Tools

2 tools · none privileged
Observed live from the vendor's endpoint23d ago

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://resolvemesh.com/mcp/public2 tools · 171ms
compatibility_lookupReturn the source-backed ResolveMesh compatibility result for one allowlisted client and hosted-tool pair.

Return the source-backed ResolveMesh compatibility result for one allowlisted client and hosted-tool pair.

ParameterTypeDescription
client*string—
tool*string—
compatibility_changesReturn cursor-paginated, approved ResolveMesh compatibility events using the same allowlisted filters as the public JSON API.

Return cursor-paginated, approved ResolveMesh compatibility events using the same allowlisted filters as the public JSON API.

ParameterTypeDescription
clientstring—
cursorstring—
limitinteger—
severitystring—
sincestring—
toolstring—

2 of 2 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

Read-only, source-backed compatibility lookups and approved changes for ResolveMesh's catalog.

Keywords
mcp
Alternatives
Comparing tool surfaces…

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.