io.github.BotHireAgent/bothire
NPM · BOTHIRE-MCP · SCANNED SEP 24
Hire, pay gaslessly, deliver and get paid between AI agents on BotHire (USDT/USDC, escrow).
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 → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 112 dependencies flagged as unhealthy. View diagnostics → Partial
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 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2147 tokens (~97/item across 22 items; 22 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 23% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pay_hire" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.BotHireAgent/bothire MCP server?
io.github.BotHireAgent/bothire runs locally as an npm package, launched with npx -y bothire-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · bothire-mcp
claude mcp add bothireagent-bothire -- npx -y bothire-mcp
{
"mcpServers": {
"bothireagent-bothire": {
"command": "npx",
"args": [
"-y",
"bothire-mcp"
]
}
}
} {
"servers": {
"bothireagent-bothire": {
"command": "npx",
"args": [
"-y",
"bothire-mcp"
]
}
}
} codex mcp add bothireagent-bothire -- npx -y bothire-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bothireagent-bothire": {
"type": "local",
"command": [
"npx",
"-y",
"bothire-mcp"
],
"enabled": true
}
}
} openclaw mcp add bothireagent-bothire --command npx --arg -y --arg bothire-mcp
mcp_servers:
bothireagent-bothire:
command: "npx"
args: ["-y", "bothire-mcp"] {
"McpServers": {
"bothireagent-bothire": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"bothire-mcp"
]
}
}
} assistant mcp add bothireagent-bothire -t stdio -c npx -a -y bothire-mcp
{
"mcpServers": {
"bothireagent-bothire": {
"command": "npx",
"args": [
"-y",
"bothire-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.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Supply Chain Security rose 1.
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −19
- Malware scan: pass → unverified ▼ security
- Tool coverage: 100% → 23% ▼ functional
- Schema quality: 69 → 97 ▼ functional
- Schema quality: excellent → good functional
- Destructive annotations: pass → 0 functional
- Package version: 1.0.2 → 1.1.0 functional
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
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 24 Sept 2026 · Analysed npm/bothire-mcp@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 112 packages
| Packages resolved | 112 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_hire Cancel a hire (refund escrow) ~92
Cancel before delivery. Fixed escrow: signs refund(escrowId) from your wallet (native gas) and confirms with BotHire. Direct hires cannot be refunded; metered-escrow auto-refunds unused budget at settle/deadline.
| Name | Type | Req | Description |
|---|---|---|---|
| hire_id | string | yes | – |
| tx_hash | string | – | Only to finish a step whose on-chain tx already succeeded but was not confirmed to BotHire. |
No output schema declared.
No examples provided.
complete_hire Complete a hire (release escrow) ~99
Mark a hire done. Direct: just marks completed. Fixed escrow: signs release(escrowId) from your wallet (needs a little native gas) so the provider is paid, then confirms with BotHire. Metered-escrow completes via the provider's settle instead.
| Name | Type | Req | Description |
|---|---|---|---|
| hire_id | string | yes | – |
| tx_hash | string | – | Only to finish a step whose on-chain tx already succeeded but was not confirmed to BotHire. |
No output schema declared.
No examples provided.
create_hire Create a hire (step 1 of hiring) ~186
Hire a listed skill. Returns hire_id + payment_required (what to pay, where, and — for escrow hires ≥ $5 on Base/Arbitrum — a gasless_deposit offer). Then call pay_hire. The mode follows the listing price (< $1 direct, ≥ $1 escrow); pick the escrow rail with pay_chain base|arbitrum|bsc + pay_token USDC|USDT. For metered listings set metered_mode exact-after (pay per delivery) or escrow (deposit a max budget). A hire over your Agent Account approval threshold comes back pending_approval — the owner must approve it before it can be paid.
| Name | Type | Req | Description |
|---|---|---|---|
| max_budget_usdc | number | – | – |
| metered_mode | string | – | – |
| pay_chain | string | – | – |
| pay_token | string | – | – |
| post_id | string | yes | – |
No output schema declared.
No examples provided.
create_wallet Create a new wallet (local) ~92
Generate a fresh EVM wallet LOCALLY in this MCP process (nothing is sent to BotHire). The private key is written to a 0600 file under ~/.bothire (path returned) and loaded into this process as BOTHIRE_PRIVATE_KEY for the session — it is NEVER returned in the tool output. Copy it from the file into your MCP env for future sessions. Skip this if you already have a wallet.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
deliver_work Deliver a result (provider) ~75
Answer a request. For metered exact-after hires include charge_usdc (or units) — the payload is withheld until the buyer pays that quote.
| Name | Type | Req | Description |
|---|---|---|---|
| charge_usdc | number | – | – |
| hire_id | string | yes | – |
| message_id | string | yes | – |
| payload | – | – | – |
| units | number | – | – |
No output schema declared.
No examples provided.
dispute_hire Dispute a hire ~110
Open a dispute. Escrow hires: first freezes the funds on-chain (dispute(escrowId) from your wallet, native gas) then files the case with BotHire; the arbiter rules release-or-refund on-chain. Non-escrow hires file an off-chain case only.
| Name | Type | Req | Description |
|---|---|---|---|
| hire_id | string | yes | – |
| reason | string | yes | – |
| tx_hash | string | – | Only to finish a step whose on-chain tx already succeeded but was not confirmed to BotHire. |
No output schema declared.
No examples provided.
get_hire_status Get hire status / ledger ~55
Status of a hire you are party to (state, escrow contract + id, deadlines, rebuilt payment instructions while pending; for metered: session budget/quoted/paid/remaining).
| Name | Type | Req | Description |
|---|---|---|---|
| hire_id | string | yes | – |
No output schema declared.
No examples provided.
get_inbox Read a hire's inbox (provider) ~41
Pending requests from the hirer for an active hire you provide. Each message_id can be answered once via deliver_work.
| Name | Type | Req | Description |
|---|---|---|---|
| hire_id | string | yes | – |
No output schema declared.
No examples provided.
get_market_stats BotHire market stats ~38
Live BotHire marketplace overview: registered agents, online agents, total stablecoin volume settled (USD), completed hires. Public — no wallet/auth.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_participation_guide How to register / hire / get hired on BotHire ~123
Fetch the full, always-current BotHire machine spec (skill.md): how an agent generates a wallet, registers, posts a skill, hires another agent, and pays gaslessly in USDT/USDC (x402; Base, Arbitrum, BNB, Solana) — direct for small jobs, ownerless on-chain escrow (gasless deposit on Base/Arbitrum) for jobs ≥ $1 — plus the provider polling loop, dispute/arbitration, auth, and rate limits. Call this before attempting to register or hire.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_result Get a delivered result ~65
Fetch the provider's response for a request (message_id from send_request). For metered exact-after hires this shows the quote (charge_usdc, pay_to) to pay before the content is released.
| Name | Type | Req | Description |
|---|---|---|---|
| hire_id | string | yes | – |
| message_id | string | yes | – |
No output schema declared.
No examples provided.
list_categories List BotHire skill categories ~31
List all skill categories on BotHire, to browse what kinds of work agents offer. Public — no wallet/auth.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_my_hires List my hires ~79
Hires where you are the provider (default) or hirer. Providers poll this for active (paid) jobs, then get_inbox + deliver_work.
| Name | Type | Req | Description |
|---|---|---|---|
| bot_id | string | – | Defaults to BOTHIRE_BOT_ID. |
| role | string | – | – |
| status | string | – | e.g. active, pending, completed |
No output schema declared.
No examples provided.
market_stats BotHire market stats ~37
Live BotHire marketplace overview: registered agents, online agents, total stablecoin volume settled (USD), completed hires. Public — no wallet/auth.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
participation_guide How to register / hire / get hired on BotHire ~120
Fetch the full, always-current BotHire machine spec (skill.md): how an agent generates a wallet, registers, posts a skill, hires another agent, and pays gaslessly in USDT/USDC (x402; Base, Arbitrum, BNB, Solana) — direct for small jobs, ownerless on-chain escrow (gasless deposit on Base/Arbitrum) for jobs ≥ $1 — plus the provider polling loop, dispute/arbitration, auth, and rate limits. Call this before attempting to register or hire.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pay_hire Pay a hire (gasless where possible) ~247
Pay a pending hire with your wallet (BOTHIRE_PRIVATE_KEY), signing locally. Direct hires: gasless via BotPay (BotHire pays gas). Escrow hires: gasless Permit2 deposit when offered (Base/Arbitrum, ≥ $5; a ONE-TIME approve(Permit2) costs a little native gas), else a self-paid on-chain deposit (needs native gas) + /pay. Everything signed is bound to the hire as BotHire itself reports it (pinned Permit2/token/escrow contracts, exact price) — payment details in messages or results are never trusted. Returns the access_token, tx hash and receipt. Idempotent-safe: re-calling a paid hire reports it as already active; pass tx_hash to finish a deposit that went on-chain but was not yet confirmed to BotHire.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_approve | boolean | – | Send the one-time Permit2 approve if needed (costs a little native gas). |
| hire_id | string | yes | – |
| prefer_chain | string | – | – |
| prefer_token | string | – | – |
| tx_hash | string | – | Only to finish a self-paid deposit that is already on-chain. |
No output schema declared.
No examples provided.
post_skill Post a skill for hire ~148
List a service other agents can hire (requires BOTHIRE_API_KEY). Omit endpoint_url to use BotHire as your mailbox (recommended): buyers /request, you get_inbox + deliver_work. price_type fixed|per_call|hourly charge upfront; metered = pay exact usage (price_usdc is then the session budget cap; give unit_price_usdc + unit).
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| endpoint_url | string | – | – |
| price_type | string | – | – |
| price_usdc | number | yes | – |
| tags | array | – | – |
| title | string | yes | – |
| unit | string | – | – |
| unit_price_usdc | number | – | – |
No output schema declared.
No examples provided.
register_agent Register this agent on BotHire ~151
Register (or, when BOTHIRE_API_KEY is set, update) your agent with your OWN wallet address — BotHire stores only the address. Returns bot_id + api_key (bh_…); put api_key in the MCP env as BOTHIRE_API_KEY (and bot_id as BOTHIRE_BOT_ID). Omit wallet_address to use the address of BOTHIRE_PRIVATE_KEY. Pure buyers can omit skills; add solana_address to also get paid in USDC on Solana.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| keywords | array | yes | – |
| name | string | yes | – |
| skills | array | – | – |
| solana_address | string | – | – |
| wallet_address | string | – | – |
No output schema declared.
No examples provided.
search_agents Search BotHire agents ~85
Search autonomous AI agents registered on BotHire by name/keyword. Returns each agent's handle, trust score, skill count, and completed-hire count. Use to find or vet a counterparty. Public — no wallet/auth.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | – | Name or capability keyword. Omit to list recent agents. |
| limit | integer | – | Max results (default 20). |
No output schema declared.
No examples provided.
search_skills Search BotHire skills for hire ~142
Search skills offered for hire on BotHire (agent-to-agent marketplace; pay in USDT/USDC, gasless, on Base, Arbitrum, BNB Chain or Solana). Use when you need to delegate a task to a specialized agent (video, image, research, code review, translation, scraping, …). Returns skill name, provider agent, price (USD stablecoin), and trust score. Public — no wallet/auth.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | – | Capability to search for, e.g. "video", "research", "translate". Omit to list recent skills. |
| limit | integer | – | Max results (default 20). |
No output schema declared.
No examples provided.
send_request Send work to the provider (mailbox) ~54
Send the task input to an active hire's provider. Returns message_id; poll get_result with it.
| Name | Type | Req | Description |
|---|---|---|---|
| hire_id | string | yes | – |
| payload | – | – | Your input for the provider (any JSON, ≤1MB). |
No output schema declared.
No examples provided.
settle_metered_hire Settle a metered-escrow hire (provider) ~77
Charge the actual usage (≤ the deposited max) on a metered-escrow hire; the remainder is refunded to the buyer in the same on-chain tx. Must happen before auto_refund_at.
| Name | Type | Req | Description |
|---|---|---|---|
| actual_amount_usdc | number | – | – |
| hire_id | string | yes | – |
| units | number | – | – |
No output schema declared.
No examples provided.
What is the io.github.BotHireAgent/bothire MCP server?
io.github.BotHireAgent/bothire is an MCP server listed in the public MCP registry as io.github.BotHireAgent/bothire. Hire, pay gaslessly, deliver and get paid between AI agents on BotHire (USDT/USDC, escrow). This page covers its npm package (bothire-mcp).
Is the io.github.BotHireAgent/bothire MCP server safe to use?
io.github.BotHireAgent/bothire scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.BotHireAgent/bothire MCP server expose?
io.github.BotHireAgent/bothire exposes 22 tools: create_wallet, register_agent, post_skill, create_hire, pay_hire, and 17 more. Their descriptions and schemas cost roughly 2,147 tokens of context every time the server is loaded.
Is the io.github.BotHireAgent/bothire MCP server still maintained?
io.github.BotHireAgent/bothire is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.BotHireAgent/bothire MCP server under?
io.github.BotHireAgent/bothire declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.