com.invokera/invokera-status

MCPcommunitylive
v1.0.0com.invokeraUnknownUpdated 1mo ago

Live health and AI-readable metadata of invokera.com. Demo of an Invokera-hosted MCP server.

Endpoint healthlive
checked 18h ago · 313ms
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.invokera
LicenseUnknown
Version1.0.0
Sourcemcp-registry
SBOMCycloneDX 1.6 ↓
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://invokera.com/r/invokera-status3 tools · 473ms
get_healthService health check with pending usage-event count. Returns: ok.

Service health check with pending usage-event count. Returns: ok.

No input schema was published for this tool.

get_llms_txtAI-readable overview of the site (llms.txt). Returns: ok.

AI-readable overview of the site (llms.txt). Returns: ok.

No input schema was published for this tool.

get_robots_txtCrawler policy (robots.txt). Returns: ok.

Crawler policy (robots.txt). Returns: ok.

No input schema was published for this tool.

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

Live health and AI-readable metadata of invokera.com. Demo of an Invokera-hosted MCP server.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

3 tools · none privileged · observed by a live tools/list probe. 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.