Hiveage MCP by usefulapi
REMOTE · HIVEAGE.USEFULAPI.IO
Manage Hiveage clients, invoices, estimates and payments; send invoices and record payments.
Available components
Last scanned (3 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3713 tokens (~132/item across 28 items; 28 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 Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 77% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.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: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 25 Oct 26 61
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 25 Oct 2026 · Probed https://hiveage.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hiveage.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://hiveage.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://hiveage.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://hiveage.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://hiveage.usefulapi.io/mcp |
| Authorisation server | https://hiveage.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hiveage.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/hiveage/ |
| http (plaintext) | http://hiveage.usefulapi.io/mcp | Inconclusive | 302 | http://hiveage.usefulapi.io/mcp |
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 →
hiveage_create_connection Create connection ~264
WRITE: create a new connection (client, vendor or company) in the account. For an organization give `name`; for an individual give first_name and last_name. Hiveage: POST /network.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| business_email | string | yes | Business email. |
| category | string | yes | organization (use name) or individual (use first_name and last_name). |
| city | string | – | – |
| country | string | – | – |
| currency | string | yes | ISO currency code, for example USD. |
| fax | string | – | – |
| first_name | string | – | First name (individual only). |
| language | string | – | Language code, default en-us (also en-uk, zh, da, nl, de, et, fil, fr, hi, it, ja, ko, ms, pt-br, ru, si, es). |
| last_name | string | – | Last name (individual only). |
| name | string | – | Organization name (organization only). |
| phone | string | – | – |
| primary_contact_first_name | string | – | – |
| primary_contact_last_name | string | – | – |
| state_name | string | – | – |
| website_url | string | – | – |
| zip_code | string | – | – |
No output schema declared.
No examples provided.
hiveage_create_contact Create contact ~115
WRITE: add a contact (name and email, used when sending statements) to a connection. Hiveage: POST /network/{hash_key}/contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| first_name | string | yes | – |
| hash_key | string | yes | The hash_key of the connection (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
| last_name | string | – | – |
| mobile | string | – | – |
| phone | string | – | – |
No output schema declared.
No examples provided.
hiveage_create_estimate Create estimate ~214
WRITE: create an estimate (quote; starts as a draft, nothing is emailed) for a connection. statement_no must be unique. Hiveage: POST /estm.
| Name | Type | Req | Description |
|---|---|---|---|
| connection_id | integer | yes | The numeric id (not the hash_key) of the connection. |
| date | string | yes | Estimate date, YYYY-MM-DD. |
| discounts | array | – | Discounts applied to the sub total. |
| expenses | array | – | Expense lines. |
| expire_date | string | yes | Expiry date, YYYY-MM-DD. |
| items | array | – | Item lines (description, price, quantity). |
| note | string | – | – |
| send_reminders | boolean | – | – |
| shipping_amounts | array | – | Shipping charges. |
| statement_no | string | yes | Unique estimate number, for example EST-001. |
| summary | string | – | – |
| tasks | array | – | Time task lines. |
| taxes | array | – | Taxes added to the sub total. |
| trips | array | – | Mileage lines. |
No output schema declared.
No examples provided.
hiveage_create_invoice Create invoice ~267
WRITE: create an invoice (starts as a draft; nothing is emailed) for a connection. statement_no must be unique. connection_id is the numeric `id` from hiveage_list_connections. Hiveage: POST /invs.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_partial_payments | boolean | – | – |
| connection_id | integer | yes | The numeric id (not the hash_key) of the connection to bill. |
| date | string | yes | Invoice date, YYYY-MM-DD. |
| discounts | array | – | Discounts applied to the sub total. |
| due_date | string | yes | Due date, YYYY-MM-DD. |
| expenses | array | – | Expense lines. |
| items | array | – | Item lines (description, price, quantity). |
| note | string | – | – |
| payment_options | array | – | Accepted payment methods. |
| po_number | string | – | – |
| send_receipts_automatically | boolean | – | – |
| send_reminders | boolean | – | – |
| shipping_amounts | array | – | Shipping charges. |
| statement_no | string | yes | Unique invoice number, for example IN-001. |
| summary | string | – | – |
| tasks | array | – | Time task lines. |
| taxes | array | – | Taxes added to the sub total. |
| trips | array | – | Mileage lines. |
No output schema declared.
No examples provided.
hiveage_create_saved_item Create saved item ~77
WRITE: save a reusable line item (name, price, unit) for statements. Hiveage: POST /categories/items.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| name | string | yes | – |
| price | – | yes | Price, for example 150.00. |
| unit | string | – | Unit label such as "hourly". |
No output schema declared.
No examples provided.
hiveage_get_connection Get connection ~71
Get one connection (client, vendor or company) by hash_key. Hiveage: GET /network/{hash_key}.
| Name | Type | Req | Description |
|---|---|---|---|
| hash_key | string | yes | The hash_key of the connection (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
No output schema declared.
No examples provided.
hiveage_get_contact Get contact ~82
Get one contact of a connection by its numeric id. Hiveage: GET /network/{hash_key}/contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| hash_key | string | yes | The hash_key of the connection (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
| id | integer | yes | The contact id. |
No output schema declared.
No examples provided.
hiveage_get_estimate Get estimate ~71
Get one estimate by hash_key, with its line items. Hiveage: GET /estm/{hash_key}.
| Name | Type | Req | Description |
|---|---|---|---|
| hash_key | string | yes | The hash_key of the estimate (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
No output schema declared.
No examples provided.
hiveage_get_invoice Get invoice ~76
Get one invoice by hash_key, with its line items, taxes, discounts and shipping. Hiveage: GET /invs/{hash_key}.
| Name | Type | Req | Description |
|---|---|---|---|
| hash_key | string | yes | The hash_key of the invoice (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
No output schema declared.
No examples provided.
hiveage_get_payment Get payment ~83
Get one payment of an invoice by its numeric id. Hiveage: GET /invs/{hash_key}/payments/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| hash_key | string | yes | The hash_key of the invoice (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
| id | integer | yes | The payment id. |
No output schema declared.
No examples provided.
hiveage_get_recurring_invoice Get recurring invoice ~70
Get one recurring invoice profile by hash_key. Hiveage: GET /rinv/{hash_key}.
| Name | Type | Req | Description |
|---|---|---|---|
| hash_key | string | yes | The hash_key of the recurring invoice (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
No output schema declared.
No examples provided.
hiveage_list_categories List saved items, expense, task or trip categories ~107
List the saved line-item templates: kind items (saved items with price and unit), expenses, tasks (with rate) or trips (with rate). Hiveage: GET /categories/{kind}.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | Which saved list to read. |
| order | string | – | Sort direction (default asc). |
| page | integer | – | Page number, starting at 1. |
| per_page | – | – | Results per page: 20 (default), 60 or 100. |
No output schema declared.
No examples provided.
hiveage_list_connection_estimates List a connection's estimates ~105
List the estimates of one connection (client). Hiveage: GET /network/{hash_key}/estimates.
| Name | Type | Req | Description |
|---|---|---|---|
| hash_key | string | yes | The hash_key of the connection (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
| page | integer | – | Page number, starting at 1. |
| per_page | – | – | Results per page: 20 (default), 60 or 100. |
No output schema declared.
No examples provided.
hiveage_list_connection_invoices List a connection's invoices ~108
List the invoices of one connection (client), by date. Hiveage: GET /network/{hash_key}/invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| hash_key | string | yes | The hash_key of the connection (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
| page | integer | – | Page number, starting at 1. |
| per_page | – | – | Results per page: 20 (default), 60 or 100. |
No output schema declared.
No examples provided.
hiveage_list_connection_recurring_invoices List a connection's recurring invoices ~111
List the recurring invoice profiles of one connection (client). Hiveage: GET /network/{hash_key}/recurring_invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| hash_key | string | yes | The hash_key of the connection (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
| page | integer | – | Page number, starting at 1. |
| per_page | – | – | Results per page: 20 (default), 60 or 100. |
No output schema declared.
No examples provided.
hiveage_list_connections List connections ~106
List connections: the companies, clients and vendors in the account's network, sorted by name. Each has a hash_key (used by other tools) and a numeric id (used as connection_id when creating invoices). Hiveage: GET /network.
| Name | Type | Req | Description |
|---|---|---|---|
| order | string | – | Sort direction (default asc). |
| page | integer | – | Page number, starting at 1. |
| per_page | – | – | Results per page: 20 (default), 60 or 100. |
No output schema declared.
No examples provided.
hiveage_list_contacts List contacts ~122
List the contacts (people with an email address for sending statements) of a connection. Hiveage: GET /network/{hash_key}/contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| hash_key | string | yes | The hash_key of the connection (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
| order | string | – | Sort direction (default asc). |
| page | integer | – | Page number, starting at 1. |
| per_page | – | – | Results per page: 20 (default), 60 or 100. |
No output schema declared.
No examples provided.
hiveage_list_estimates List estimates ~74
List estimates (quotes), sorted by date. Hiveage: GET /estm.
| Name | Type | Req | Description |
|---|---|---|---|
| order | string | – | Sort direction (default asc). |
| page | integer | – | Page number, starting at 1. |
| per_page | – | – | Results per page: 20 (default), 60 or 100. |
No output schema declared.
No examples provided.
hiveage_list_invoices List invoices ~86
List invoices (state draft, viewed, sent, paid or partial) with totals, sorted by date. Hiveage: GET /invs.
| Name | Type | Req | Description |
|---|---|---|---|
| order | string | – | Sort direction (default asc). |
| page | integer | – | Page number, starting at 1. |
| per_page | – | – | Results per page: 20 (default), 60 or 100. |
No output schema declared.
No examples provided.
hiveage_list_payments List invoice payments ~103
List the payments entered on an invoice. Hiveage: GET /invs/{hash_key}/payments.
| Name | Type | Req | Description |
|---|---|---|---|
| hash_key | string | yes | The hash_key of the invoice (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
| page | integer | – | Page number, starting at 1. |
| per_page | – | – | Results per page: 20 (default), 60 or 100. |
No output schema declared.
No examples provided.
hiveage_list_recurring_invoice_invoices List invoices generated by a recurring invoice ~110
List the invoices a recurring invoice profile has generated. Hiveage: GET /rinv/{hash_key}/invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| hash_key | string | yes | The hash_key of the recurring invoice (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
| page | integer | – | Page number, starting at 1. |
| per_page | – | – | Results per page: 20 (default), 60 or 100. |
No output schema declared.
No examples provided.
hiveage_list_recurring_invoices List recurring invoices ~68
List recurring invoice profiles (interval, next billing date, occurrences). Hiveage: GET /rinv.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, starting at 1. |
| per_page | – | – | Results per page: 20 (default), 60 or 100. |
No output schema declared.
No examples provided.
hiveage_mark_payment_realized Mark payment realized ~99
WRITE: mark an offline (unrealized) payment as realized, so it counts as received. Hiveage: POST /invs/{hash_key}/payments/{id}/mark_as_realized.
| Name | Type | Req | Description |
|---|---|---|---|
| hash_key | string | yes | The hash_key of the invoice (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
| id | integer | yes | The payment id. |
No output schema declared.
No examples provided.
hiveage_record_payment Record invoice payment ~145
WRITE: enter a payment received on an invoice (changes its paid and due totals). Offline payments (cash, check, bank_transfer) are saved as unrealized until marked realized. Hiveage: POST /invs/{hash_key}/payments.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | – | yes | Payment amount, for example 10.00. |
| date | string | – | Date received, YYYY-MM-DD. |
| details | string | – | Payment description. |
| hash_key | string | yes | The hash_key of the invoice (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
| payment_method | string | yes | How the invoice was paid. |
No output schema declared.
No examples provided.
hiveage_send_estimate Send estimate by email ~193
WRITE, SENDS EMAIL: email an estimate to the client (default template, or custom). Cannot be undone. Hiveage: POST /estm/{hash_key}/deliver.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment | boolean | – | Attach the PDF (custom delivery only). |
| blind_copies | array | – | BCC addresses (custom delivery only). |
| confirm | boolean | yes | Must be true: this emails real people from the Hiveage account. |
| hash_key | string | yes | The hash_key of the estimate (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
| message | string | – | Email body (custom delivery only). |
| recipients | array | – | Custom TO addresses (all of recipients, subject and message are then needed). Omit for the default template and the connection's contacts. |
| subject | string | – | Email subject (custom delivery only). |
No output schema declared.
No examples provided.
hiveage_send_invoice Send invoice by email ~204
WRITE, SENDS EMAIL: email an invoice to the client (the default invoice template to the connection's contacts, or a custom recipient/subject/message). Cannot be undone. Hiveage: POST /invs/{hash_key}/deliver.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment | boolean | – | Attach the PDF (custom delivery only). |
| blind_copies | array | – | BCC addresses (custom delivery only). |
| confirm | boolean | yes | Must be true: this emails real people from the Hiveage account. |
| hash_key | string | yes | The hash_key of the invoice (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
| message | string | – | Email body (custom delivery only). |
| recipients | array | – | Custom TO addresses (all of recipients, subject and message are then needed). Omit for the default template and the connection's contacts. |
| subject | string | – | Email subject (custom delivery only). |
No output schema declared.
No examples provided.
hiveage_send_invoice_reminder Send invoice reminder by email ~197
WRITE, SENDS EMAIL: email a payment reminder for an invoice (default reminder template, or custom). Cannot be undone. Hiveage: POST /invs/{hash_key}/reminder.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment | boolean | – | Attach the PDF (custom delivery only). |
| blind_copies | array | – | BCC addresses (custom delivery only). |
| confirm | boolean | yes | Must be true: this emails real people from the Hiveage account. |
| hash_key | string | yes | The hash_key of the invoice (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
| message | string | – | Email body (custom delivery only). |
| recipients | array | – | Custom TO addresses (all of recipients, subject and message are then needed). Omit for the default template and the connection's contacts. |
| subject | string | – | Email subject (custom delivery only). |
No output schema declared.
No examples provided.
hiveage_update_contact Update contact ~124
WRITE: change fields of a contact (only the fields you pass are sent). Hiveage: PUT /network/{hash_key}/contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | – | |
| first_name | string | – | – |
| hash_key | string | yes | The hash_key of the connection (a short string such as "bCbFYNj3RFM2uQ"), not its numeric id. |
| id | integer | yes | The contact id. |
| last_name | string | – | – |
| mobile | string | – | – |
| phone | string | – | – |
No output schema declared.
No examples provided.
How do I install the Hiveage MCP by usefulapi server?
Hiveage MCP by usefulapi is a hosted endpoint at https://hiveage.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · hiveage.usefulapi.io
claude mcp add --transport http io-usefulapi-hiveage 'https://hiveage.usefulapi.io/mcp'
What is the Hiveage MCP by usefulapi server?
Hiveage MCP by usefulapi is listed in the public MCP registry as io.usefulapi/hiveage. Manage Hiveage clients, invoices, estimates and payments; send invoices and record payments. This page covers its hosted endpoint (https://hiveage.usefulapi.io/mcp).
Is the Hiveage MCP by usefulapi server safe to use?
Hiveage MCP by usefulapi scores 61 out of 100 on VerifyMCP. 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 Hiveage MCP by usefulapi server expose?
Hiveage MCP by usefulapi exposes 28 tools: hiveage_list_connections, hiveage_get_connection, hiveage_list_connection_invoices, hiveage_list_connection_estimates, hiveage_list_connection_recurring_invoices, and 23 more. Their descriptions and schemas cost roughly 3,452 tokens of context every time the server is loaded.
Does the Hiveage MCP by usefulapi server require authentication?
Yes. Hiveage MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Hiveage MCP by usefulapi server still maintained?
Hiveage MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.