timeahead-mcp@0.1.0
VERIFIED· not startedPublisher claims: "MCP server for timeahead.in — live trust scores for MCP servers" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
TIMEAHEAD_API_KEYConfiguration, not credentials: TIMEAHEAD_BASE_URL, TIMEAHEAD_TIMEOUT- Where it talks to
- timeahead.in (its own)
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard. It asks for TIMEAHEAD_API_KEY and talks to timeahead.in. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-19 and scored it 88/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
respx.get(f'{BASE}/history/mcp-server-postgres/').mock(return_value=httpx.Response(200, json=payload))Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.respx.get(f'{BASE}/score/mcp-server-postgres/').mock(return_value=httpx.Response(200, json=payload))Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.'install_command': 'npx mcp-server-postgres',Fix: Pin versions and sources; vendor anything fetched at install time.respx.get(f'{BASE}/findings/mcp-server-postgres/').mock(return_value=httpx.Response(200, json=payload))Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.respx.get(f'{BASE}/detail/mcp-server-postgres/').mock(return_value=httpx.Response(200, json=payload))Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for timeahead-mcp@0.1.0 as of 2 h ago. This is the package itself, not its dependencies.