trakkr-mcp

MCPcommunity
v0.20.0io.github.macklpgrUnknownUpdated 1d ago

AI visibility analytics for brands across citations, prompts, competitors, research, and reports.

Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, 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 →
1d agoLast update
Reads these credentials
  • TRAKKR_API_KEYAPI keyoptional

    Optional MCP connect token from Trakkr Settings > Developer. If omitted, the server starts Trakkr's device authorization flow.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.macklpgr
LicenseUnknown
Version0.20.0
Sourcemcp-registry
Trust Status
10/100Unrated
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 · not run+0/30
This entry exposes no inspectable source (a hosted endpoint), so there is nothing to scan. Publish an npm package or link a public repository to become scannable.
Obfuscation / exfil scan · not run+0/20
This entry exposes no inspectable source (a hosted endpoint), so there is nothing to scan. Publish an npm package or link a public repository to become scannable.
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
DependenciesNot audited
Tool surface
Security scanNot runHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

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

Tools

Not probed yet

Forge has not completed a tools/list handshake against this endpoint, so it holds no observation of what the server exposes. Nothing here says it exposes nothing.

About

AI visibility analytics for brands across citations, prompts, competitors, research, and reports.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.