Method CRM MCP by usefulapi
REMOTE · METHOD-CRM.USEFULAPI.IO
Query Method CRM customers, leads, activities and invoices; create and update records.
Available components
Last scanned (2 hours 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 Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3339 tokens (~208/item across 16 items; 16 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 Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% 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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 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.2.0 → 1.2.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://method-crm.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 method-crm.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://method-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://method-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp" Protected resource metadata
| Document | https://method-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://method-crm.usefulapi.io/mcp |
| Authorisation server | https://method-crm.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://method-crm.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/method-crm/ |
| http (plaintext) | http://method-crm.usefulapi.io/mcp | Inconclusive | 302 | http://method-crm.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 →
method_count_records Count records ~90
How many records a table has, optionally matching a filter (same filter syntax as method_query_records). Cheap: call it before paging through a big table. GET /api/v1/tables/{table}/count.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Filter expression. |
| table | string | yes | Table name exactly as method_list_tables shows it, e.g. Customer, Contacts, Activity, Invoice, Estimate. |
No output schema declared.
No examples provided.
method_create_activity Log an activity ~311
WRITE: logs an activity (call, email, to-do, note) on a customer/lead. entity_id is the Customer RecordID; contact_id is the Contact RecordID (not the Customer's; method_list_contacts finds it). The text goes in Comments. Prefer activity_type_id (read it from an existing activity of that type) over the caption activity_type: a caption that matches zero or several options is silently dropped. Method requires an assignee on standard accounts. The reply re-reads the activity so you can check the links were stored (field names are account-specific; method_get_table_fields with table Activity shows them). It does not email anyone. Not idempotent. POST /api/v1/tables/Activity.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_type | string | – | Activity type caption, e.g. Call. Use only if you have no id. |
| activity_type_id | integer | – | ActivityType_RecordID from an existing activity of the wanted type. |
| assigned_to_id | integer | – | Method user id of the owner (method_get_account). |
| comments | string | yes | The note body. |
| contact_id | integer | – | The Contact RecordID. |
| due | string | – | Due/start time, YYYY-MM-DDTHH:mm:ss. |
| entity_id | integer | yes | The Customer (entity) RecordID the activity belongs to, so it shows in its history. |
| status_id | integer | – | ActivityStatus_RecordID (account-defined, e.g. Not Started / Completed). |
No output schema declared.
No examples provided.
method_create_customer Create customer or lead ~346
WRITE: creates a record in Method's Customer table. is_lead true = a Customer Lead (does not sync to the accounting system); is_lead false = a full customer, which Method syncs to QuickBooks/Xero (it appears there too). Method also creates the primary Contact; its RecordID is returned as contact_id when it could be found (use it, not the customer id, to link activities). Name is required (for a person with no company use "First Last"). `extra_fields` sets other fields by their exact names (see method_get_table_fields, table Customer). Not idempotent: calling twice creates two records, so search first (method_search_customers). POST /api/v1/tables/Customer.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to_id | integer | – | Owner: a Method user id (method_get_account, or the Users table). |
| string | – | – | |
| extra_fields | object | – | Field name -> value, exactly as method_get_table_fields names them (case-sensitive; a misspelled name is silently ignored by Method). For a dropdown/linked field send the integer id in its `_RecordID… |
| first_name | string | – | – |
| is_lead | boolean | yes | true = lead (not synced to accounting), false = customer (synced to QuickBooks/Xero). |
| last_name | string | – | – |
| lead_status | string | – | Account-defined lead status, e.g. Open (leads only). |
| name | string | yes | Display name of the customer or lead. |
| phone | string | – | – |
No output schema declared.
No examples provided.
method_create_record Create a record ~232
WRITE: creates a record in any table that allows it (method_list_tables shows canCreate), e.g. Estimate, Invoice, Item, Vendor. For customers/leads and activities use the dedicated tools. Field names are case-sensitive and a wrong one is silently ignored: read them with method_get_table_fields first, and send dropdown links as their `_RecordID` integer. Creating accounting records (Invoice, Estimate, Customer ...) makes Method sync them to QuickBooks/Xero. Child lines (InvoiceLine ...) are not supported here. Not idempotent. Returns the new RecordID. POST /api/v1/tables/{table}.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | yes | Field name -> value, exactly as method_get_table_fields names them (case-sensitive; a misspelled name is silently ignored by Method). For a dropdown/linked field send the integer id in its `_RecordID… |
| table | string | yes | Table name exactly as method_list_tables shows it, e.g. Customer, Contacts, Activity, Invoice, Estimate. |
No output schema declared.
No examples provided.
method_get_account Get API key owner ~50
Who the API key acts as: the Method user behind it (id and name; use the id as an assignee). Also a cheap check that the key works. GET /api/v1/me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
method_get_file_url Get file download link ~77
A temporary download link (valid 20 minutes) for an attached file, by the file id from method_list_files. The link works without the API key: share it only with someone allowed to see the file. GET /api/v1/files/{id}/url.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | File id (a GUID). |
No output schema declared.
No examples provided.
method_get_record Get record ~201
One record by RecordID from any table. Pass `select` to limit the columns; `expand` names a related CHILD table whose rows are embedded (e.g. InvoiceLine on Invoice; at most 50 rows); a parent such as a contact's Entity is not expanded: read it with its own RecordID (Entity_RecordID). GET /api/v1/tables/{table}/{recordId}.
| Name | Type | Req | Description |
|---|---|---|---|
| expand | string | – | A child table to embed (a table with a dropdown field to this one), e.g. InvoiceLine on Invoice. At most 50 child rows. |
| record_id | integer | yes | The record's RecordID. |
| select | array | – | Field names to return (case-sensitive, from method_get_table_fields). Without a select Method returns hundreds of columns per row. |
| table | string | yes | Table name exactly as method_list_tables shows it, e.g. Customer, Contacts, Activity, Invoice, Estimate. |
No output schema declared.
No examples provided.
method_get_table_fields Get table fields ~106
The exact field names of a table with type, whether required, creatable and mutable, and for dropdowns the table they reference. Use it to pick `select` fields and to name fields in create/update calls (names are case-sensitive and wrong ones are silently ignored). GET /api/v1/tables/{table}/fields.
| Name | Type | Req | Description |
|---|---|---|---|
| table | string | yes | Table name exactly as method_list_tables shows it, e.g. Customer, Contacts, Activity, Invoice, Estimate. |
No output schema declared.
No examples provided.
method_list_activities List activities ~271
List activities (calls, emails, to-dos, notes), newest first. Filter by the entity they belong to, the assigned user or a due-date window. The note text is in Comments. Override `select` for other fields (method_get_table_fields with table Activity). GET /api/v1/tables/Activity.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to_id | integer | – | Only activities assigned to this user id (method_get_account or the Users table). |
| due_after | string | – | ISO 8601 date-time WITH a timezone (Z or +hh:mm), e.g. 2026-10-01T00:00:00Z. |
| due_before | string | – | ISO 8601 date-time WITH a timezone (Z or +hh:mm), e.g. 2026-10-01T00:00:00Z. |
| entity_id | integer | – | Only activities of this entity (Customer RecordID). |
| select | array | – | Field names to return (case-sensitive, from method_get_table_fields). Without a select Method returns hundreds of columns per row. |
| skip | integer | – | Rows to skip (default 0). Pass the previous reply's next_skip. |
| top | integer | – | Rows per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
method_list_contacts List contacts ~194
List contacts (people), optionally those of one customer/lead entity (entity_id = the Customer's RecordID) or matching text in name/email/phone. Returns RecordID, name, email, phone, the entity link and active flag. Use a Contact's RecordID (not the Customer's) when linking activities. GET /api/v1/tables/Contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | integer | – | Only contacts of this entity (the Customer/Vendor RecordID). |
| select | array | – | Field names to return (case-sensitive, from method_get_table_fields). Without a select Method returns hundreds of columns per row. |
| skip | integer | – | Rows to skip (default 0). Pass the previous reply's next_skip. |
| text | string | – | Matches contacts whose Name, Email or Phone contains this text. |
| top | integer | – | Rows per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
method_list_files List files on a record ~85
List the files attached to a record (name, size, who added it, id). Use the id with method_get_file_url. GET /api/v1/files.
| Name | Type | Req | Description |
|---|---|---|---|
| record_id | integer | yes | The record's RecordID. |
| table | string | yes | Table name exactly as method_list_tables shows it, e.g. Customer, Contacts, Activity, Invoice, Estimate. |
No output schema declared.
No examples provided.
method_list_invoices List invoices ~227
List invoices, newest first, optionally only unpaid ones (BalanceRemaining > 0), one customer's (customer_id = Customer RecordID) or created since a time. Returns reference number, customer, dates, amount and balance; override `select` for other fields. For totals use method_query_records with `apply`. GET /api/v1/tables/Invoice.
| Name | Type | Req | Description |
|---|---|---|---|
| created_since | string | – | ISO 8601 date-time WITH a timezone (Z or +hh:mm), e.g. 2026-10-01T00:00:00Z. |
| customer_id | integer | – | Only invoices of this customer (Customer RecordID). |
| select | array | – | Field names to return (case-sensitive, from method_get_table_fields). Without a select Method returns hundreds of columns per row. |
| skip | integer | – | Rows to skip (default 0). Pass the previous reply's next_skip. |
| top | integer | – | Rows per page, 1-100 (default 25). |
| unpaid_only | boolean | – | Only invoices with an outstanding balance. |
No output schema declared.
No examples provided.
method_list_tables List tables ~67
List every table on this Method account (standard QuickBooks/Xero/Method tables and custom ones) with its source and whether it can be created, updated or deleted. Tables differ per account: call this before querying a table you are unsure of. GET /api/v1/tables.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
method_query_records Query records ~367
Query any table (Customer, Contacts, Activity, Invoice, Estimate, Item, Users, custom tables ...). Always pass `select`. `filter` uses OData-style syntax: strings in single quotes, dates as '2026-05-26T00:00:00Z' with Z or an offset, operators eq ne lt gt le ge and or not, functions contains(Name,'x') startswith() endswith(); e.g. "BalanceRemaining gt 0 and DueDate lt '2026-10-01T00:00:00Z'". `apply` runs server-side aggregation instead of listing rows, e.g. "aggregate(BalanceRemaining with sum as Outstanding)" or "groupby((Customer), aggregate(Amount with sum as Total))". Default order is RecordID ascending (stable paging); page with next_skip. GET /api/v1/tables/{table}.
| Name | Type | Req | Description |
|---|---|---|---|
| apply | string | – | Aggregation, e.g. "aggregate($count as Total)"; ignores paging. |
| filter | string | – | Filter expression, e.g. "IsLeadStatusOnly eq true and contains(Name,'Smith')". |
| orderby | string | – | Sort, e.g. "RecordID desc" or "TotalBalance desc,RecordID". |
| select | array | – | Field names to return (case-sensitive, from method_get_table_fields). Without a select Method returns hundreds of columns per row. |
| skip | integer | – | Rows to skip (default 0). Pass the previous reply's next_skip. |
| table | string | yes | Table name exactly as method_list_tables shows it, e.g. Customer, Contacts, Activity, Invoice, Estimate. |
| top | integer | – | Rows per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
method_search_customers Search customers and leads ~218
Find customers and leads (the Customer table: Customers & Leads in Method) by text in the name or email, by lead/customer type, or list them all. Returns RecordID, name, email, phone, lead flag and status; override `select` for other fields (see method_get_table_fields with table Customer). Page with next_skip. GET /api/v1/tables/Customer.
| Name | Type | Req | Description |
|---|---|---|---|
| active_only | boolean | – | Only active records (IsActive true). |
| kind | string | – | leads = IsLeadStatusOnly true, customers = false (default all). |
| select | array | – | Field names to return (case-sensitive, from method_get_table_fields). Without a select Method returns hundreds of columns per row. |
| skip | integer | – | Rows to skip (default 0). Pass the previous reply's next_skip. |
| text | string | – | Matches records whose Name or Email contains this text (case-insensitive). |
| top | integer | – | Rows per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
method_update_record Update a record ~238
WRITE: changes fields on one record (PATCH: only the fields you pass change). Field names are case-sensitive and Method silently ignores wrong or read-only names, so the reply re-reads the record and shows the stored values of the fields you sent: check them. Linked fields are changed through their `_RecordID` integer field. Updating accounting records (Customer, Invoice ...) makes Method sync the change to QuickBooks/Xero; setting IsLeadStatusOnly to false converts a lead into a synced customer. There is no delete tool. PATCH /api/v1/tables/{table}/{recordId}.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | yes | Field name -> value, exactly as method_get_table_fields names them (case-sensitive; a misspelled name is silently ignored by Method). For a dropdown/linked field send the integer id in its `_RecordID… |
| record_id | integer | yes | The record's RecordID. |
| table | string | yes | Table name exactly as method_list_tables shows it, e.g. Customer, Contacts, Activity, Invoice, Estimate. |
No output schema declared.
No examples provided.
How do I install the Method CRM MCP by usefulapi server?
Method CRM MCP by usefulapi is a hosted endpoint at https://method-crm.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 · method-crm.usefulapi.io
claude mcp add --transport http io-usefulapi-method-crm 'https://method-crm.usefulapi.io/mcp'
What is the Method CRM MCP by usefulapi server?
Method CRM MCP by usefulapi is listed in the public MCP registry as io.usefulapi/method-crm. Query Method CRM customers, leads, activities and invoices; create and update records. This page covers its hosted endpoint (https://method-crm.usefulapi.io/mcp).
Is the Method CRM MCP by usefulapi server safe to use?
Method CRM 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 Method CRM MCP by usefulapi server expose?
Method CRM MCP by usefulapi exposes 16 tools: method_get_account, method_list_tables, method_get_table_fields, method_query_records, method_count_records, and 11 more. Their descriptions and schemas cost roughly 3,080 tokens of context every time the server is loaded.
Does the Method CRM MCP by usefulapi server require authentication?
Yes. Method CRM 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 Method CRM MCP by usefulapi server still maintained?
Method CRM 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.