tinyfish-guided-research-mcp@1.0.0
VERIFIED· not startedPublisher claims: "Auditable deep-research MCP server powered by TinyFish Search and Fetch" 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
DATABASE_URLTINYFISH_API_KEYConfiguration, not credentials: ENABLE_CROSSREF_CHECKS, ENABLE_OPENALEX_CHECKS, FETCH_TOP_N_PER_QUERY, LOG_FORMAT, MAX_ATOMICITY_SPLIT_DEPTH, MAX_CANDIDATE_CONTEXTS, MAX_FETCH_PER_RETRIEVAL, MAX_PARALLEL_SUBAGENTS, MIN_CITATION_WORKS_PER_CLAIM, MIN_INDEPENDENT_WORKS, OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_SERVICE_NAME, RESEARCH_DB_PATH, SERVICE_VERSION, TINYFISH_BASE_BACKOFF, TINYFISH_FETCH_CONCURRENCY, TINYFISH_FETCH_URL, TINYFISH_FETCH_URLS_RPM, TINYFISH_MAX_RETRIES, TINYFISH_SEARCH_CONCURRENCY, TINYFISH_SEARCH_RPM, TINYFISH_SEARCH_URL- Where it talks to
- no vendor host named in the codeAlso tinyfish.ai, doi.org, crossref.org, openalex.org — not the publisher's domain; check what for before connecting.
- 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, and read the third-party hosts first. The code names tinyfish.ai, doi.org, crossref.org, openalex.org as well as its own vendor. The guard injects DATABASE_URL, TINYFISH_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
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 91/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 · 1 s · 2 scenarios · 0 deviationsStatic findings
run: npx -y @modelcontextprotocol/inspector --cli uv run tinyfish-guided-research-mcp --method tools/list --format jsonFix: Pin versions and sources; vendor anything fetched at install time.No other findings across 5,954 lines in 31 files.
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 tinyfish-guided-research-mcp@1.0.0 as of 2 h ago. This is the package itself, not its dependencies.