io.github.plus8bit/hosaka
NPM · HOSAKA-MCP · SCANNED AUG 22
Company facts for AI agents: which vendors a company uses, proven from DNS. Paid in USDC.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security13
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
- No install/post-install scripts declared.Pass
- Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 506 tokens (~126/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · hosaka-mcp
claude mcp add plus8bit-hosaka -- npx -y hosaka-mcp
codex mcp add plus8bit-hosaka -- npx -y hosaka-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"plus8bit-hosaka": {
"type": "local",
"command": [
"npx",
"-y",
"hosaka-mcp"
],
"enabled": true
}
}
} openclaw mcp add plus8bit-hosaka --command npx --arg -y --arg hosaka-mcp
mcp_servers:
plus8bit-hosaka:
command: "npx"
args: ["-y", "hosaka-mcp"] {
"mcpServers": {
"plus8bit-hosaka": {
"command": "npx",
"args": [
"-y",
"hosaka-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Aug 26 42
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Aug 2026 · Analysed npm/hosaka-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
hosaka_contacts How to reach a company ~102
Everything hosaka_dossier returns, plus every contact point the company publishes about itself — 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 $0.02 in USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Company domain, for example figma.com. A URL or a www prefix is fine. |
No output schema declared.
No examples provided.
hosaka_dossier Full company dossier ~101
Everything hosaka_lookup returns, plus every third-party vendor the company can be proven to use — CRM, email, analytics, cloud, HR, payments — each with the DNS record, SPF include or loaded script that proves it. Also returns raw DNS, registration, certificate and site facts. Costs $0.07 in USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Company domain, for example figma.com. A URL or a www prefix is fine. |
No output schema declared.
No examples provided.
hosaka_lookup Look up a company ~82
Fast 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 $0.01 in USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Company domain, for example figma.com. A URL or a www prefix is fine. |
No output schema declared.
No examples provided.
hosaka_people People who work at a company ~91
Everything hosaka_dossier returns, plus named people who work at the company, sourced from a people-data provider. Cheaper than buying the contacts alone elsewhere. Use hosaka_contacts instead when a published support or sales address would answer the question. Costs $0.25 in USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Company domain, for example figma.com. A URL or a www prefix is fine. |
No output schema declared.
No examples provided.