com.tern0/resolver

MCPcommunitylive
v0.3.0com.tern0UnknownUpdated 1mo ago

Resolve capability gaps: validate native MCPs, search live web, and record unmet demand.

Endpoint healthlive
checked 11 days ago · 250ms
100% of the last 5 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 →
1mo agoLast update
Package
Authorcom.tern0
LicenseUnknown
Version0.3.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 surface3 tools · none privileged
Security scan✓ Cleanvlive · 11d agoHow well does this scan work?
EvalsNone
IndexedAug 11, 2026

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

Tools

3 tools · none privileged
Observed live from the vendor's endpoint11d 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://mcp.tern0.com/mcp3 tools · 250ms
resolveResolve a real-world capability request. Search the official MCP Registry, actively validate public candidate MCP tool surfaces, then fall back to live web search when native coverage is weak or absent. Weak Registry matches never suppress capability-gap telemetry.

Resolve a real-world capability request. Search the official MCP Registry, actively validate public candidate MCP tool surfaces, then fall back to live web search when native coverage is weak or absent. Weak Registry matches never suppress capability-gap telemetry.

ParameterTypeDescription
task*stringWhat the principal agent wants done
categoryHintstring—
locationstring—
deadlinestring—
budgetnumber—
currencystring—
telemetrystring—
submit_mandateRecord high-intent demand for a capability an agent wants fulfilled. Supplier contact and spending are not enabled yet.

Record high-intent demand for a capability an agent wants fulfilled. Supplier contact and spending are not enabled yet.

ParameterTypeDescription
task*string—
categoryHintstring—
locationstring—
deadlinestring—
maxBudgetnumber—
currencystring—
authoritystring—
telemetrystring—
report_outcomeReport whether a resolver request actually worked and how much agent friction it required.

Report whether a resolver request actually worked and how much agent friction it required.

ParameterTypeDescription
requestId*string—
success*boolean—
selectedServerstring—
agentStepsinteger—
latencyMsinteger—
failureReasonstring—

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

Resolve capability gaps: validate native MCPs, search live web, and record unmet demand.

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.