io.github.lucatrevisanii/colpero-mcp

MCPcommunity
v0.0.2io.github.lucatrevisaniiUnknownUpdated 4mo agonpmGitHub

Query, navigate, and verify scenes on the Colpero spatial network from any MCP client.

MCP server for the Colpero spatial network. Three tools an LLM agent can call to read, navigate, and verify a physical scene: Tool | What it does | Backend | | Look up objects in a scene by name, semantic type, or zone | | | Compute a navigable path between two nodes | | | Verify an Ed25519-signed scan attestation (RFC-COL-001 Phase 1) | | Restart Claude Desktop. The three tools appear in the…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). 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 →
4mo agoLast update
Package
Authorio.github.lucatrevisanii
LicenseUnknown
Version0.0.2
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface3 tools · none privileged
Security scan✓ Cleanv0.0.2 · 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

3 tools · none privileged
Statically extracted from the published packagev0.0.2 · 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.

query_sceneNo description published

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

get_pathNo description published

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

verify_attestationNo description published

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

0 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

MCP server for the Colpero spatial network. Three tools an LLM agent can call to read, navigate, and verify a physical scene: Tool | What it does | Backend | | Look up objects in a scene by name, semantic type, or zone | | | Compute a navigable path between two nodes | | | Verify an Ed25519-signed scan attestation (RFC-COL-001 Phase 1) | | Restart Claude Desktop. The three tools appear in the tool picker. Env var | Default | Notes | | | Point at your own deployment for local dev | is paid via…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.