Hosaka MCP server
io.github.plus8bit/hosaka·v0.3.2·1 starsCompany facts for AI agents: which vendors a company uses, proven from DNS. Paid in USDC.
1 stars55 downloads/wk
Reviews
Write oneNobody has reviewed Hosaka yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Hosaka tools (5)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
hosaka_contactsEverything hosaka_dossier returns, plus every contact point the company publishes about itself \u2014 support and sales email addresses, phone numbers and social accounts, read from its own site. Use this when the question is how to reach the company. For named individuals who work there, use hosaka_people instead. Costs … in USDC.
hosaka_dossierEverything hosaka_lookup returns, plus every third-party vendor the company can be proven to use \u2014 CRM, email, analytics, cloud, HR, payments \u2014 each with the DNS record, SPF include or loaded script that proves it. Also returns raw DNS, registration, certificate and site facts. Costs … in USDC.
hosaka_executivesFinds the decision makers at a company from its domain alone: owners, founders, C-level, partners, VPs, heads and directors, each with title, location and profile link, plus everything hosaka_dossier returns. Reach for it when the question is who to approach about buying something. Use hosaka_people to see anyone who works there regardless of level. Costs … in USDC.
hosaka_lookupFast facts about a company from its domain: how old the domain is, its registrar, mail and DNS providers, whether DMARC and HTTPS are configured, and how many third-party vendors are visible. Costs … in USDC.
hosaka_peopleFinds the people who work at a company from its domain alone: named employees with job title, seniority, location and profile link, plus everything hosaka_dossier returns. Reach for it when the domain is all you have, because most people-data tools want an email or a profile URL first. Use hosaka_contacts instead when a published support address would answer. Costs … in USDC.
Public scan report
scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it
- Code scan2 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 54 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Hosaka compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 78/100
- higher than 57% of 48,243 servers
- Tools
- 5
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 1
- more than 65% of 28,706 servers
- Downloads a week
- 55
- more than 44% of 12,306 servers with a package
What its tools let an agent do: 5 read
Install Hosaka in Claude Code, Cursor or VS Code
Runs npx -y hosaka-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add hosaka -- npx -y hosaka-mcp
What the publisher says
From the Hosaka repository's README, as published. We do not edit it. Read it on GitHub
deadchannel & Hosaka
Two services that sell to AI agents over x402, paid per call in USDC. No signup, no API key, no subscription — an agent calls, pays, and gets an answer.
Agents can install Hosaka as a skill, which tells them what it is for and when to reach for it:
npx skills add plus8bit/deadchannel/skills/hosaka --yesHosaka — company data for agents
Available as an MCP server, so any MCP client can buy from it directly:
npx -y hosaka-mcp{
"mcpServers": {
"hosaka": {
"command": "npx",
"args": ["-y", "hosaka-mcp"],
"env": { "HOSAKA_PRIVATE_KEY": "0x…" }
}
}
}HOSAKAPRIVATEKEY is a wallet holding a little USDC on Base. Four tools at four prices, so a cheap question never pays for an expensive answer:
Why the dossier is worth having. A company proves it owns its domain to every SaaS product it buys by placing a DNS verification record, and authorises every sender it uses in its SPF record. Those two lists are a purchase history the company published itself.
Asking for figma.com returns Anthropic, OpenAI, Adobe, Atlassian, MongoDB Atlas, Greenhouse, Docusign, Stripe, Notion, Dropbox and Zendesk — each with the exact record that proves it, so a buyer can check rather than trust.
Page fingerprints require a loaded script or CDN host, never a mention: a site listing a vendor's logo among its integrations is not a site that uses it.
Live at hosaka-agents.vercel.app.
deadchannel — a risk oracle for x402 endpoints
Give it a URL, it tells an agent whether that endpoint is alive, honestly priced, and safe to call — without spending a cent.
Roughly 17% of probed x402 endpoints are dead or traps, and the Bazaar discovery layer ships no ranking, quality, or reputation signal by its own admission. An agent picking from that catalog is guessing with real money.
What it checks
Every verdict comes from unpaid 402 responses, which is what makes it cheap enough to run across a whole catalog.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Hosaka: common questions
- Is Hosaka MCP server safe?
- Mostly: it is graded B (78/100). Read the Hosaka safety report
- How do I install Hosaka?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Hosaka need an API key?
- Yes. The registry entry asks for
HOSAKA_PRIVATE_KEY. - Is Hosaka maintained?
- The last commit was 61 days ago (2026-09-05). The latest release is v0.3.2.
- How does Hosaka compare with other MCP servers?
- safety score 78/100 (higher than 57% of 48,243 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.