Bidsketch MCP by usefulapi
REMOTE · BIDSKETCH.USEFULAPI.IO
Read Bidsketch clients, proposals, fees and templates; create and update clients, proposals, fees.
Available components
Last scanned (1 hour ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
Category CRM and Sales
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 Usability80
- 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 3371 tokens (~116/item across 29 items; 29 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 Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 71% 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
- We read all 29 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 30 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
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 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.1.0 → 1.1.3 functional
- 24 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://bidsketch.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 bidsketch.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://bidsketch.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://bidsketch.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://bidsketch.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://bidsketch.usefulapi.io/mcp |
| Authorisation server | https://bidsketch.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bidsketch.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/bidsketch/ |
| http (plaintext) | http://bidsketch.usefulapi.io/mcp | Inconclusive | 302 | http://bidsketch.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 →
bidsketch_add_proposal_fee Add a fee to a proposal ~166
WRITE: add a fee line to a proposal; it changes the proposal's price. Fixed fees take amount as the total; hourly, monthly and yearly fees take amount per unit and a quantity. POST /proposals/{id}/fees.json.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| category | string | – | – |
| description | string | yes | HTML-formatted content, for example <p>Hello</p>. |
| feetype | string | yes | – |
| name | string | yes | – |
| optional | boolean | – | true = an optional item the client may choose. |
| proposal_id | integer | yes | The proposal id (a positive integer). |
| quantity | integer | – | Quantity for calculated fees. |
| unit | string | – | Unit label, only for custom fees. |
No output schema declared.
No examples provided.
bidsketch_add_proposal_section Add a section to a proposal ~99
WRITE: add a text section to a proposal, as an opening or closing section. POST /proposals/{id}/sections.json.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | HTML-formatted content, for example <p>Hello</p>. |
| name | string | yes | – |
| proposal_id | integer | yes | The proposal id (a positive integer). |
| sectiontype | string | yes | opening (shown first) or closing (shown last). |
No output schema declared.
No examples provided.
bidsketch_create_client Create a client ~242
WRITE: create a client in Bidsketch. first_name, last_name and email are required (put a company name in `name`). Some Bidsketch plans cap the number of clients (HTTP 426 when reached). POST /clients.json.
| Name | Type | Req | Description |
|---|---|---|---|
| address_field_one | string | – | – |
| address_field_two | string | – | – |
| alt_phone | string | – | – |
| city | string | – | – |
| country | string | – | – |
| string | yes | Client's primary email address (required by Bidsketch). | |
| first_name | string | yes | Client's first name (required by Bidsketch). |
| last_name | string | yes | Client's last name (required by Bidsketch). |
| name | string | – | Client's full name or company name. |
| notes | string | – | Notes about the client (plain text, not escaped). |
| other_contact | object | – | Secondary contact; first_name, last_name and email are required when given. |
| phone | string | – | – |
| postal_zip | string | – | – |
| state | string | – | – |
| website | string | – | – |
No output schema declared.
No examples provided.
bidsketch_create_fee Create a saved fee ~107
WRITE: save a reusable fee on the account (it is not added to any proposal). POST /fees.json.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| category | string | – | – |
| description | string | – | HTML-formatted content, for example <p>Hello</p>. |
| feetype | string | yes | – |
| name | string | yes | – |
| quantity | integer | – | Quantity for calculated fees. |
| unit | string | – | Unit label, only for custom fees. |
No output schema declared.
No examples provided.
bidsketch_create_proposal Create a proposal ~270
WRITE: create a proposal for a client, optionally from a template (template_id from bidsketch_list_templates, which copies its sections and fees). The proposal is created as a draft; this tool does not send anything to the client. Some plans cap the number of proposals (HTTP 426). POST /proposals.json or POST /templates/{id}/proposals.json.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | The client the proposal is for (from bidsketch_list_clients) (a positive integer). |
| currency | string | – | ISO currency code, e.g. USD. |
| description | string | yes | Summary of the proposal (the vendor docs list it with name and client_id as the minimum). |
| discount | number | – | Discount as a decimal fraction (0.1 = 10%). |
| name | string | yes | Proposal name. |
| proposal_date | string | – | Proposal date as m/d/yyyy, e.g. 10/26/2026. |
| tax | number | – | Tax as a decimal fraction (0.1 = 10%). |
| tax2 | number | – | Secondary tax as a decimal fraction (0.1 = 10%). |
| template_id | integer | – | Optional template to copy sections and fees from (a positive integer). |
No output schema declared.
No examples provided.
bidsketch_create_section Create a saved section ~76
WRITE: save a reusable content section on the account (it is not added to any proposal). POST /sections.json.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| description | string | – | HTML-formatted content, for example <p>Hello</p>. |
| name | string | yes | – |
| sectiontype | string | yes | – |
No output schema declared.
No examples provided.
bidsketch_get_client Get a client ~55
Get one client with full contact details, address, notes and secondary contact. GET /clients/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | The client id from bidsketch_list_clients (a positive integer). |
No output schema declared.
No examples provided.
bidsketch_get_fee Get a saved fee ~55
Get one saved fee with amount, quantity, unit and description. GET /fees/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| fee_id | integer | yes | The saved fee id from bidsketch_list_fees (a positive integer). |
No output schema declared.
No examples provided.
bidsketch_get_proposal Get a proposal ~77
Get one proposal: status, client, currency, fee subtotals and total, tax/discount, settings and counts of its opening sections, fees and closing sections. GET /proposals/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| proposal_id | integer | yes | The proposal id from bidsketch_list_proposals (a positive integer). |
No output schema declared.
No examples provided.
bidsketch_get_proposal_content Get a proposal's content ~56
Get the full content of a proposal in order: opening sections, fees and closing sections. GET /proposals/{id}/content.json.
| Name | Type | Req | Description |
|---|---|---|---|
| proposal_id | integer | yes | The proposal id (a positive integer). |
No output schema declared.
No examples provided.
bidsketch_get_proposal_fee Get a proposal fee ~66
Get one fee line of a proposal. GET /proposals/{id}/fees/{fee_id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| fee_id | integer | yes | The proposal fee id (a positive integer). |
| proposal_id | integer | yes | The proposal id (a positive integer). |
No output schema declared.
No examples provided.
bidsketch_get_proposal_section Get a proposal section ~69
Get one section of a proposal with its HTML description. GET /proposals/{id}/sections/{section_id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| proposal_id | integer | yes | The proposal id (a positive integer). |
| section_id | integer | yes | The proposal section id (a positive integer). |
No output schema declared.
No examples provided.
bidsketch_get_proposal_stats Get proposal stats ~33
Proposal statistics for the account (the total number of proposals). GET /proposals/stats.json.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bidsketch_get_section Get a saved section ~50
Get one saved section with its HTML description. GET /sections/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| section_id | integer | yes | The saved section id from bidsketch_list_sections (a positive integer). |
No output schema declared.
No examples provided.
bidsketch_get_template Get a proposal template ~54
Get one template with the saved sections and fees it is made of. GET /templates/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | integer | yes | The template id from bidsketch_list_templates (a positive integer). |
No output schema declared.
No examples provided.
bidsketch_list_client_proposals List a client's proposals ~90
List the proposals of one client with status (Pending, Viewed, Accepted, Declined) and draft flag. GET /clients/{id}/proposals.json.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | The client id (a positive integer). |
| page | integer | – | Page number (default 1). |
| per_page | integer | – | Results per page (default and maximum 100). |
No output schema declared.
No examples provided.
bidsketch_list_clients List clients ~67
List the clients (people or companies proposals are prepared for) with id, name, email and phone. GET /clients.json.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1). |
| per_page | integer | – | Results per page (default and maximum 100). |
No output schema declared.
No examples provided.
bidsketch_list_fees List saved fees ~62
List the reusable fees saved on the account with category, type and total. GET /fees.json.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1). |
| per_page | integer | – | Results per page (default and maximum 100). |
No output schema declared.
No examples provided.
bidsketch_list_proposal_fees List a proposal's fees ~85
List the fee lines of one proposal with type, totals and the optional flag. GET /proposals/{id}/fees.json.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1). |
| per_page | integer | – | Results per page (default and maximum 100). |
| proposal_id | integer | yes | The proposal id (a positive integer). |
No output schema declared.
No examples provided.
bidsketch_list_proposal_sections List a proposal's sections ~80
List the text sections of one proposal (opening and closing). GET /proposals/{id}/sections.json.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1). |
| per_page | integer | – | Results per page (default and maximum 100). |
| proposal_id | integer | yes | The proposal id (a positive integer). |
No output schema declared.
No examples provided.
bidsketch_list_proposals List proposals ~70
List all proposals with name, status (Pending, Viewed, Accepted, Declined), draft flag and dates. GET /proposals.json.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1). |
| per_page | integer | – | Results per page (default and maximum 100). |
No output schema declared.
No examples provided.
bidsketch_list_sections List saved sections ~64
List the reusable content sections saved on the account with category and type (opening or closing). GET /sections.json.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1). |
| per_page | integer | – | Results per page (default and maximum 100). |
No output schema declared.
No examples provided.
bidsketch_list_templates List proposal templates ~67
List the proposal templates saved on the account. Use a template id with bidsketch_create_proposal. GET /templates.json.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1). |
| per_page | integer | – | Results per page (default and maximum 100). |
No output schema declared.
No examples provided.
bidsketch_update_client Update a client ~220
WRITE: change fields of an existing client; only the fields you pass are sent and overwrite the old values. PUT /clients/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| address_field_one | string | – | – |
| address_field_two | string | – | – |
| alt_phone | string | – | – |
| city | string | – | – |
| client_id | integer | yes | The client id (a positive integer). |
| country | string | – | – |
| string | – | Client's primary email address. | |
| first_name | string | – | Client's first name (a person). |
| last_name | string | – | Client's last name (a person). |
| name | string | – | Client's full name or company name. |
| notes | string | – | Notes about the client (plain text, not escaped). |
| other_contact | object | – | Secondary contact; first_name, last_name and email are required when given. |
| phone | string | – | – |
| postal_zip | string | – | – |
| state | string | – | – |
| website | string | – | – |
No output schema declared.
No examples provided.
bidsketch_update_fee Update a saved fee ~171
WRITE: change a saved fee; only the fields you pass are sent. Proposals that already use it keep their own copy. PUT /fees/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Fixed fee: the total. Calculated fee: the amount per unit. |
| category | string | – | – |
| description | string | – | HTML-formatted content, for example <p>Hello</p>. |
| fee_id | integer | yes | The saved fee id (a positive integer). |
| feetype | string | – | fixed = a total; hourly/monthly/yearly = amount per unit x quantity; custom = your own unit label. |
| name | string | – | – |
| quantity | integer | – | Quantity for calculated fees. |
| unit | string | – | Unit label, only for custom fees. |
No output schema declared.
No examples provided.
bidsketch_update_proposal Update a proposal ~197
WRITE: change fields of a proposal; only the fields you pass are sent and overwrite the old values. PUT /proposals/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | – | Move the proposal to this client (a positive integer). |
| currency | string | – | ISO currency code, e.g. USD. |
| description | string | – | Summary of the proposal. |
| discount | number | – | Discount as a decimal fraction (0.1 = 10%). |
| name | string | – | Proposal name. |
| proposal_date | string | – | Proposal date as m/d/yyyy, e.g. 10/26/2026. |
| proposal_id | integer | yes | The proposal id (a positive integer). |
| tax | number | – | Tax as a decimal fraction (0.1 = 10%). |
| tax2 | number | – | Secondary tax as a decimal fraction (0.1 = 10%). |
No output schema declared.
No examples provided.
bidsketch_update_proposal_fee Update a proposal fee ~206
WRITE: change a fee line of a proposal (changes its price); only the fields you pass are sent. PUT /proposals/{id}/fees/{fee_id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Fixed fee: the total. Calculated fee: the amount per unit. |
| category | string | – | – |
| description | string | – | HTML-formatted content, for example <p>Hello</p>. |
| fee_id | integer | yes | The proposal fee id (a positive integer). |
| feetype | string | – | fixed = a total; hourly/monthly/yearly = amount per unit x quantity; custom = your own unit label. |
| name | string | – | – |
| optional | boolean | – | true = an optional item the client may choose. |
| proposal_id | integer | yes | The proposal id (a positive integer). |
| quantity | integer | – | Quantity for calculated fees. |
| unit | string | – | Unit label, only for custom fees. |
No output schema declared.
No examples provided.
bidsketch_update_proposal_section Update a proposal section ~134
WRITE: change a section of a proposal; only the fields you pass are sent and overwrite the old values. PUT /proposals/{id}/sections/{section_id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| description | string | – | HTML-formatted content, for example <p>Hello</p>. |
| name | string | – | – |
| proposal_id | integer | yes | The proposal id (a positive integer). |
| section_id | integer | yes | The proposal section id (a positive integer). |
| sectiontype | string | – | Where the section appears: opening (first) or closing (last). |
No output schema declared.
No examples provided.
bidsketch_update_section Update a saved section ~115
WRITE: change a saved section; only the fields you pass are sent. Proposals that already use it keep their own copy. PUT /sections/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| description | string | – | HTML-formatted content, for example <p>Hello</p>. |
| name | string | – | – |
| section_id | integer | yes | The saved section id (a positive integer). |
| sectiontype | string | – | Where the section appears: opening (first) or closing (last). |
No output schema declared.
No examples provided.
How do I install the Bidsketch MCP by usefulapi server?
Bidsketch MCP by usefulapi is a hosted endpoint at https://bidsketch.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 · bidsketch.usefulapi.io
claude mcp add --transport http io-usefulapi-bidsketch 'https://bidsketch.usefulapi.io/mcp'
What is the Bidsketch MCP by usefulapi server?
Bidsketch MCP by usefulapi is listed in the public MCP registry as io.usefulapi/bidsketch. Read Bidsketch clients, proposals, fees and templates; create and update clients, proposals, fees. This page covers its hosted endpoint (https://bidsketch.usefulapi.io/mcp).
Is the Bidsketch MCP by usefulapi server safe to use?
Bidsketch MCP by usefulapi scores 62 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 Bidsketch MCP by usefulapi server expose?
Bidsketch MCP by usefulapi exposes 29 tools: bidsketch_list_clients, bidsketch_get_client, bidsketch_list_client_proposals, bidsketch_create_client, bidsketch_update_client, and 24 more. Their descriptions and schemas cost roughly 3,103 tokens of context every time the server is loaded.
Does the Bidsketch MCP by usefulapi server require authentication?
Yes. Bidsketch 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 Bidsketch MCP by usefulapi server still maintained?
Bidsketch 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.