How Mercury’s scores are calculated

Point an agent at llms.txt or agent-oriented docsweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

• [claimed-docs] https://docs.mercury.com/llms.txt“Mercury API docs state: 'For AI agents: visit https://docs.mercury.com/llms.txt for an index of all pages formatted in Markdown and endpoints in OpenAPI. Append .md to any documentation page URL to get its markdown version.'”
• [probe] https://docs.mercury.com/llms.txt“PROBE llms.txt: HTTP 200 at https://docs.mercury.com/llms.txt # Mercury API Documentation > Documentation for Mercury API Append .md to any documentation page URL to get its markdo”
• [probe] https://docs.mercury.com/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.mercury.com/openapi.json, https://docs.mercury.com/swagger.json, https://docs.mercury.com/api/openapi.json, https://docs.mercury.com/.well-known/openapi.json)”
• [probe] https://docs.mercury.com/openapi.json“PROBE openapi-reverify (2026-09-14): all conventional public spec paths still 404 (https://docs.mercury.com/openapi.json -> 404, https://docs.mercury.com/swagger.json -> 404, https://docs.mercury.com/api/openapi.json -> 404, https://docs.mercury.com/.well-known/openapi.json -> 404). The docs hub page config confirms this is deliberate: the ReadMe project contains OpenAPI 3.0 definitions (mwb-openapi.yaml, onboarding-openapi.yaml) but ships "showOpenAPIDownload":false and "openapiVisibility":"admin" — the machine-readable spec exists internally and is not publicly downloadable. The same page serves the interactive "Try It" runner (HTTP 200).”

Run the product headlessly / in CI for automationweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

• [claimed-docs] https://mercury.com/api“Run Mercury operations from your terminal, a script, or a CI pipeline”
• [claimed-docs] https://mercury.com/api“Issue scoped API tokens with fine-grained permissions”
• [probe] https://github.com/MercuryTechnologies/mercury-cli“PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The official command-line interface for Mercury.'). Installed via the documented installer `curl -sSf https://cli.mercury.com/install.sh | sh` (HTTP 200) → downloaded mercury_0.11.8_macos_arm64.zip, verified checksum, installed binary. Ran `mercury --version` → "mercury version 0.11.8" (exit 0). Ran `mercury --help` → full command tree: Auth (login/logout/status), Onboarding (apply), Resources (accounts, cards, categories, credit, customers, events, invoices, org, payments, recipients, safes, statements, transactions, treasury, users, webhooks), Utility (upgrade), plus --format/--api-key/--environment flags (sandbox|production). No authentication or account access was performed.”
• [claimed-docs] https://docs.mercury.com/docs/using-mercury-sandbox.md“Our Sandbox environment is designed to make it easy for you to test API calls in a safe, simulated version of Mercury — no real money involved.”
• [claimed-docs] https://docs.mercury.com/docs/using-mercury-sandbox.md“Docs, "Using the Mercury Sandbox for Testing": sign up for a sandbox account at https://sandbox.mercury.com/signup; "When making API requests, make sure they're pointed to our sandbox base URL: https://api-sandbox.mercury.com/api/v1/"; "If you're using Sandbox for testing OAuth2 integrations, the base URL is https://oauth2-sandbox.mercury.com/"; the sandbox home page comes "pre-loaded with dummy data including organizations, accounts, transactions, and account balances to allow testing", and "Tokens created outside of the sandbox (like in production) won't work here."”
• [claimed-docs] https://github.com/MercuryTechnologies/mercury-go“Official Go SDK, MercuryTechnologies/mercury-go: "The Mercury Go library provides convenient access to the Mercury REST API from applications written in Go... It is generated with Stainless", installed via `go get -u github.com/MercuryTechnologies/mercury-go@v0.13.11` (requires Go 1.22+). (No official npm or PyPI SDK exists — only community packages such as n8n-nodes-mercury, announced in Mercury's changelog as a "community node".)”
• [claimed-docs] https://mercury.com/api“Test safely in the sandbox, then swap one URL for production”

Plug MCP servers into this product so it can use their toolsweight 3

n/a — not applicable to this product: excluded from numerator and denominator

• [claimed-docs] https://docs.mercury.com/docs/connecting-mercury-mcp.md“Set the MCP server URL to `https://mcp.mercury.com/mcp`.”
• [probe] https://mcp.mercury.com/mcp“PROBE mcp-runtime: Mercury's MCP is a remote, hosted, streamable-HTTP server (per docs, no stdio/npx variant exists — "Mercury does not offer a non-hosted MCP at this time"). Unauthenticated JSON-RPC `initialize` POST to https://mcp.mercury.com/mcp → HTTP 401 with header `www-authenticate: Bearer error="invalid_token", error_description="Missing Authorization header"` (served via Cloudflare/Express). GET https://mcp.mercury.com/.well-known/oauth-protected-resource → 200 `{"resource":"https://mcp.mercury.com/mcp","authorization_servers":["https://mcp.mercury.com/"],"scopes_supported":["read","offline_access"]}`. GET https://mcp.mercury.com/.well-known/oauth-authorization-server → 200, confirms RFC 7591 dynamic client registration endpoints (register/authorize/token) with PKCE S256 required. Confirms a live, OAuth-gated, read-only remote MCP server; no unauthenticated tool listing is possible by design. No real account was authenticated against.”
• [probe] https://docs.mercury.com/docs/supported-tools-on-mercury-mcp.md“PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getAccount, getAccountCards, getAccountStatements, getTransaction, getAccounts, listCategories, listCredit, getOrganization, getRecipient, getRecipients, listTransactions, getTreasury, getTreasuryTransactions, getCard, listCards, getUser, getUsers, getWebhook, getWebhooks, getTransactionById, getTreasuryStatements, listSendMoneyApprovalRequests, getSafeRequest, getSafeRequests, listRecipientsAttachments, getAttachment, getCustomer, listCustomers, getInvoice, listInvoices, listInvoiceAttachments. Consistent with docs stating the hosted MCP has 'read-only access to certain types of information.'”

Connect an agent via an official MCP serverweight 3

3 (weight) × 8 (quality) × 1.0 (full) = 24.0 of 30 max

• [claimed-docs] https://docs.mercury.com/docs/connecting-mercury-mcp.md“Set the MCP server URL to `https://mcp.mercury.com/mcp`.”
• [claimed-docs] https://docs.mercury.com/docs/supported-tools-on-mercury-mcp.md“What's my balance today?”
• [claimed-docs] https://docs.mercury.com/docs/what-is-mercury-mcp.md“Track your balance - easy access to account level balances, with ability to download statements as PDFs”
• [claimed-docs] https://docs.mercury.com/docs/security-best-practices.md“The ability to revoke access at any time from your Mercury dashboard”
• [probe] https://mcp.mercury.com/mcp“PROBE mcp-runtime: Mercury's MCP is a remote, hosted, streamable-HTTP server (per docs, no stdio/npx variant exists — "Mercury does not offer a non-hosted MCP at this time"). Unauthenticated JSON-RPC `initialize` POST to https://mcp.mercury.com/mcp → HTTP 401 with header `www-authenticate: Bearer error="invalid_token", error_description="Missing Authorization header"` (served via Cloudflare/Express). GET https://mcp.mercury.com/.well-known/oauth-protected-resource → 200 `{"resource":"https://mcp.mercury.com/mcp","authorization_servers":["https://mcp.mercury.com/"],"scopes_supported":["read","offline_access"]}`. GET https://mcp.mercury.com/.well-known/oauth-authorization-server → 200, confirms RFC 7591 dynamic client registration endpoints (register/authorize/token) with PKCE S256 required. Confirms a live, OAuth-gated, read-only remote MCP server; no unauthenticated tool listing is possible by design. No real account was authenticated against.”
• [probe] https://docs.mercury.com/docs/supported-tools-on-mercury-mcp.md“PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getAccount, getAccountCards, getAccountStatements, getTransaction, getAccounts, listCategories, listCredit, getOrganization, getRecipient, getRecipients, listTransactions, getTreasury, getTreasuryTransactions, getCard, listCards, getUser, getUsers, getWebhook, getWebhooks, getTransactionById, getTreasuryStatements, listSendMoneyApprovalRequests, getSafeRequest, getSafeRequests, listRecipientsAttachments, getAttachment, getCustomer, listCustomers, getInvoice, listInvoices, listInvoiceAttachments. Consistent with docs stating the hosted MCP has 'read-only access to certain types of information.'”

Use an official CLIweight 2

2 (weight) × 9 (quality) × 1.0 (full) = 18.0 of 20 max

• [probe] https://github.com/MercuryTechnologies/mercury-cli“PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The official command-line interface for Mercury.'). Installed via the documented installer `curl -sSf https://cli.mercury.com/install.sh | sh` (HTTP 200) → downloaded mercury_0.11.8_macos_arm64.zip, verified checksum, installed binary. Ran `mercury --version` → "mercury version 0.11.8" (exit 0). Ran `mercury --help` → full command tree: Auth (login/logout/status), Onboarding (apply), Resources (accounts, cards, categories, credit, customers, events, invoices, org, payments, recipients, safes, statements, transactions, treasury, users, webhooks), Utility (upgrade), plus --format/--api-key/--environment flags (sandbox|production). No authentication or account access was performed.”
• [claimed-docs] https://github.com/MercuryTechnologies/mercury-skills“Official MercuryTechnologies/mercury-skills repo, "Mercury Skills Directory": "Agent skills that drive the Mercury CLI. Each skill is a self-contained SKILL.md following the Agent Skills format" — installable via `npx skills add git@github.com:MercuryTechnologies/mercury-skills.git`, with skills like mercury-analyze-spend, mercury-detect-anomaly, and mercury-receipt-upload; "The CLI handles auth itself: set MERCURY_API_KEY in your environment, or run mercury login".”
• [claimed-docs] https://mercury.com/api“Run Mercury operations from your terminal, a script, or a CI pipeline”

Drive the product through a documented public APIweight 3

3 (weight) × 9 (quality) × 1.0 (full) = 27.0 of 30 max

• [claimed-docs] https://docs.mercury.com“Mercury API endpoint catalog: List all transactions, Get a transaction by ID, Update transaction metadata, Upload a transaction attachment; Categories: List/Create/Edit/Delete a category; Statements: Download account statement PDF; Merchants: List merchants; Treasury: Get treasury transactions, Get treasury account statements.”
• [claimed-docs] https://docs.mercury.com“Accounts Receivable API: Customers (List/Create/Get/Update/Delete a customer); Invoices (List/Create/Get/Update/Cancel an invoice, Download invoice PDF); Webhooks (Create/Update/Verify/Get/Delete webhook endpoints); Events (Get all events, Get event by ID).”
• [claimed-docs] https://docs.mercury.com/llms.txt“Mercury API docs state: 'For AI agents: visit https://docs.mercury.com/llms.txt for an index of all pages formatted in Markdown and endpoints in OpenAPI. Append .md to any documentation page URL to get its markdown version.'”
• [claimed-docs] https://docs.mercury.com“OAuth2 API: Start OAuth2 web flow; Obtain an access token — Mercury supports OAuth2 authorization for third-party/programmatic access alongside API tokens.”
• [claimed-docs] https://mercury.com/api“Issue scoped API tokens with fine-grained permissions”
• [probe] https://github.com/MercuryTechnologies/mercury-cli“PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The official command-line interface for Mercury.'). Installed via the documented installer `curl -sSf https://cli.mercury.com/install.sh | sh` (HTTP 200) → downloaded mercury_0.11.8_macos_arm64.zip, verified checksum, installed binary. Ran `mercury --version` → "mercury version 0.11.8" (exit 0). Ran `mercury --help` → full command tree: Auth (login/logout/status), Onboarding (apply), Resources (accounts, cards, categories, credit, customers, events, invoices, org, payments, recipients, safes, statements, transactions, treasury, users, webhooks), Utility (upgrade), plus --format/--api-key/--environment flags (sandbox|production). No authentication or account access was performed.”
• [claimed-docs] https://docs.mercury.com/docs/using-mercury-sandbox.md“Docs, "Using the Mercury Sandbox for Testing": sign up for a sandbox account at https://sandbox.mercury.com/signup; "When making API requests, make sure they're pointed to our sandbox base URL: https://api-sandbox.mercury.com/api/v1/"; "If you're using Sandbox for testing OAuth2 integrations, the base URL is https://oauth2-sandbox.mercury.com/"; the sandbox home page comes "pre-loaded with dummy data including organizations, accounts, transactions, and account balances to allow testing", and "Tokens created outside of the sandbox (like in production) won't work here."”
• [claimed-docs] https://docs.mercury.com/reference“Every endpoint page on the API Reference hub (docs.mercury.com/reference, ReadMe) embeds a live request runner and generated code samples: "Click `Try It!` to start a request and see the response here! Or choose an example:", with a Language picker (Shell, Node, Ruby, PHP, Python), a Bearer credentials field, per-endpoint path/query params, and 200/404 response schemas — e.g. "get https://api.mercury.com/api/v1/account/{accountId}/cards".”
• [claimed-docs] https://github.com/MercuryTechnologies/mercury-go“Official Go SDK, MercuryTechnologies/mercury-go: "The Mercury Go library provides convenient access to the Mercury REST API from applications written in Go... It is generated with Stainless", installed via `go get -u github.com/MercuryTechnologies/mercury-go@v0.13.11` (requires Go 1.22+). (No official npm or PyPI SDK exists — only community packages such as n8n-nodes-mercury, announced in Mercury's changelog as a "community node".)”
• [probe] https://docs.mercury.com/openapi.json“PROBE openapi-reverify (2026-09-14): all conventional public spec paths still 404 (https://docs.mercury.com/openapi.json -> 404, https://docs.mercury.com/swagger.json -> 404, https://docs.mercury.com/api/openapi.json -> 404, https://docs.mercury.com/.well-known/openapi.json -> 404). The docs hub page config confirms this is deliberate: the ReadMe project contains OpenAPI 3.0 definitions (mwb-openapi.yaml, onboarding-openapi.yaml) but ships "showOpenAPIDownload":false and "openapiVisibility":"admin" — the machine-readable spec exists internally and is not publicly downloadable. The same page serves the interactive "Try It" runner (HTTP 200).”

Issue scoped/least-privilege API credentials for an agentweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

• [claimed-docs] https://mercury.com/api“Issue scoped API tokens with fine-grained permissions”
• [claimed-docs] https://docs.mercury.com/docs/getting-started.md“There are three types of tokens: read-only, read-write, and custom.”
• [claimed-docs] https://docs.mercury.com/docs/security-best-practices.md“The ability to revoke access at any time from your Mercury dashboard”
• [claimed-docs] https://docs.mercury.com“OAuth2 API: Start OAuth2 web flow; Obtain an access token — Mercury supports OAuth2 authorization for third-party/programmatic access alongside API tokens.”
• [probe] https://mcp.mercury.com/mcp“PROBE mcp-runtime: Mercury's MCP is a remote, hosted, streamable-HTTP server (per docs, no stdio/npx variant exists — "Mercury does not offer a non-hosted MCP at this time"). Unauthenticated JSON-RPC `initialize` POST to https://mcp.mercury.com/mcp → HTTP 401 with header `www-authenticate: Bearer error="invalid_token", error_description="Missing Authorization header"` (served via Cloudflare/Express). GET https://mcp.mercury.com/.well-known/oauth-protected-resource → 200 `{"resource":"https://mcp.mercury.com/mcp","authorization_servers":["https://mcp.mercury.com/"],"scopes_supported":["read","offline_access"]}`. GET https://mcp.mercury.com/.well-known/oauth-authorization-server → 200, confirms RFC 7591 dynamic client registration endpoints (register/authorize/token) with PKCE S256 required. Confirms a live, OAuth-gated, read-only remote MCP server; no unauthenticated tool listing is possible by design. No real account was authenticated against.”
• [probe] https://docs.mercury.com/docs/supported-tools-on-mercury-mcp.md“PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getAccount, getAccountCards, getAccountStatements, getTransaction, getAccounts, listCategories, listCredit, getOrganization, getRecipient, getRecipients, listTransactions, getTreasury, getTreasuryTransactions, getCard, listCards, getUser, getUsers, getWebhook, getWebhooks, getTransactionById, getTreasuryStatements, listSendMoneyApprovalRequests, getSafeRequest, getSafeRequests, listRecipientsAttachments, getAttachment, getCustomer, listCustomers, getInvoice, listInvoices, listInvoiceAttachments. Consistent with docs stating the hosted MCP has 'read-only access to certain types of information.'”

Build against official SDKsweight 2

2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max

• [claimed-docs] https://github.com/MercuryTechnologies/mercury-go“Official Go SDK, MercuryTechnologies/mercury-go: "The Mercury Go library provides convenient access to the Mercury REST API from applications written in Go... It is generated with Stainless", installed via `go get -u github.com/MercuryTechnologies/mercury-go@v0.13.11` (requires Go 1.22+). (No official npm or PyPI SDK exists — only community packages such as n8n-nodes-mercury, announced in Mercury's changelog as a "community node".)”
• [claimed-docs] https://github.com/MercuryTechnologies/mercury-skills“Official MercuryTechnologies/mercury-skills repo, "Mercury Skills Directory": "Agent skills that drive the Mercury CLI. Each skill is a self-contained SKILL.md following the Agent Skills format" — installable via `npx skills add git@github.com:MercuryTechnologies/mercury-skills.git`, with skills like mercury-analyze-spend, mercury-detect-anomaly, and mercury-receipt-upload; "The CLI handles auth itself: set MERCURY_API_KEY in your environment, or run mercury login".”
• [probe] https://github.com/MercuryTechnologies/mercury-cli“PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The official command-line interface for Mercury.'). Installed via the documented installer `curl -sSf https://cli.mercury.com/install.sh | sh` (HTTP 200) → downloaded mercury_0.11.8_macos_arm64.zip, verified checksum, installed binary. Ran `mercury --version` → "mercury version 0.11.8" (exit 0). Ran `mercury --help` → full command tree: Auth (login/logout/status), Onboarding (apply), Resources (accounts, cards, categories, credit, customers, events, invoices, org, payments, recipients, safes, statements, transactions, treasury, users, webhooks), Utility (upgrade), plus --format/--api-key/--environment flags (sandbox|production). No authentication or account access was performed.”
• [probe] https://docs.mercury.com/openapi.json“PROBE openapi-reverify (2026-09-14): all conventional public spec paths still 404 (https://docs.mercury.com/openapi.json -> 404, https://docs.mercury.com/swagger.json -> 404, https://docs.mercury.com/api/openapi.json -> 404, https://docs.mercury.com/.well-known/openapi.json -> 404). The docs hub page config confirms this is deliberate: the ReadMe project contains OpenAPI 3.0 definitions (mwb-openapi.yaml, onboarding-openapi.yaml) but ships "showOpenAPIDownload":false and "openapiVisibility":"admin" — the machine-readable spec exists internally and is not publicly downloadable. The same page serves the interactive "Try It" runner (HTTP 200).”
• [claimed-docs] https://mercury.com/api“Pull balances, list transactions, and initiate ACH transfers — all through a single REST API”
• [claimed-docs] https://mercury.com/api“Test safely in the sandbox, then swap one URL for production”

Subscribe to events via webhooksweight 2

2 (weight) × 7 (quality) × 1.0 (full) = 14.0 of 20 max

• [claimed-docs] https://docs.mercury.com“Accounts Receivable API: Customers (List/Create/Get/Update/Delete a customer); Invoices (List/Create/Get/Update/Cancel an invoice, Download invoice PDF); Webhooks (Create/Update/Verify/Get/Delete webhook endpoints); Events (Get all events, Get event by ID).”
• [probe] https://github.com/MercuryTechnologies/mercury-cli“PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The official command-line interface for Mercury.'). Installed via the documented installer `curl -sSf https://cli.mercury.com/install.sh | sh` (HTTP 200) → downloaded mercury_0.11.8_macos_arm64.zip, verified checksum, installed binary. Ran `mercury --version` → "mercury version 0.11.8" (exit 0). Ran `mercury --help` → full command tree: Auth (login/logout/status), Onboarding (apply), Resources (accounts, cards, categories, credit, customers, events, invoices, org, payments, recipients, safes, statements, transactions, treasury, users, webhooks), Utility (upgrade), plus --format/--api-key/--environment flags (sandbox|production). No authentication or account access was performed.”

Explore an interactive API reference with runnable examplesweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

• [claimed-docs] https://docs.mercury.com/reference“Every endpoint page on the API Reference hub (docs.mercury.com/reference, ReadMe) embeds a live request runner and generated code samples: "Click `Try It!` to start a request and see the response here! Or choose an example:", with a Language picker (Shell, Node, Ruby, PHP, Python), a Bearer credentials field, per-endpoint path/query params, and 200/404 response schemas — e.g. "get https://api.mercury.com/api/v1/account/{accountId}/cards".”
• [claimed-docs] https://docs.mercury.com/docs/using-mercury-sandbox.md“Docs, "Using the Mercury Sandbox for Testing": sign up for a sandbox account at https://sandbox.mercury.com/signup; "When making API requests, make sure they're pointed to our sandbox base URL: https://api-sandbox.mercury.com/api/v1/"; "If you're using Sandbox for testing OAuth2 integrations, the base URL is https://oauth2-sandbox.mercury.com/"; the sandbox home page comes "pre-loaded with dummy data including organizations, accounts, transactions, and account balances to allow testing", and "Tokens created outside of the sandbox (like in production) won't work here."”
• [probe] https://docs.mercury.com/openapi.json“PROBE openapi-reverify (2026-09-14): all conventional public spec paths still 404 (https://docs.mercury.com/openapi.json -> 404, https://docs.mercury.com/swagger.json -> 404, https://docs.mercury.com/api/openapi.json -> 404, https://docs.mercury.com/.well-known/openapi.json -> 404). The docs hub page config confirms this is deliberate: the ReadMe project contains OpenAPI 3.0 definitions (mwb-openapi.yaml, onboarding-openapi.yaml) but ships "showOpenAPIDownload":false and "openapiVisibility":"admin" — the machine-readable spec exists internally and is not publicly downloadable. The same page serves the interactive "Try It" runner (HTTP 200).”
• [claimed-docs] https://docs.mercury.com/docs/using-mercury-sandbox.md“Our Sandbox environment is designed to make it easy for you to test API calls in a safe, simulated version of Mercury — no real money involved.”

Download a machine-readable API spec (OpenAPI or equivalent)weight 2

2 (weight) × 4 (quality) × 0.3 (disputed) = 2.4 of 20 max

• [claimed-docs] https://docs.mercury.com/llms.txt“Mercury API docs state: 'For AI agents: visit https://docs.mercury.com/llms.txt for an index of all pages formatted in Markdown and endpoints in OpenAPI. Append .md to any documentation page URL to get its markdown version.'”
• [probe] https://docs.mercury.com/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.mercury.com/openapi.json, https://docs.mercury.com/swagger.json, https://docs.mercury.com/api/openapi.json, https://docs.mercury.com/.well-known/openapi.json)”
• [probe] https://docs.mercury.com/openapi.json“PROBE openapi-reverify (2026-09-14): all conventional public spec paths still 404 (https://docs.mercury.com/openapi.json -> 404, https://docs.mercury.com/swagger.json -> 404, https://docs.mercury.com/api/openapi.json -> 404, https://docs.mercury.com/.well-known/openapi.json -> 404). The docs hub page config confirms this is deliberate: the ReadMe project contains OpenAPI 3.0 definitions (mwb-openapi.yaml, onboarding-openapi.yaml) but ships "showOpenAPIDownload":false and "openapiVisibility":"admin" — the machine-readable spec exists internally and is not publicly downloadable. The same page serves the interactive "Try It" runner (HTTP 200).”

Test against a sandbox environment without touching production dataweight 1

1 (weight) × 9 (quality) × 1.0 (full) = 9.0 of 10 max

• [claimed-docs] https://mercury.com/api“Test safely in the sandbox, then swap one URL for production”
• [claimed-docs] https://docs.mercury.com/docs/using-mercury-sandbox.md“Our Sandbox environment is designed to make it easy for you to test API calls in a safe, simulated version of Mercury — no real money involved.”
• [claimed-docs] https://docs.mercury.com/docs/using-mercury-sandbox.md“Docs, "Using the Mercury Sandbox for Testing": sign up for a sandbox account at https://sandbox.mercury.com/signup; "When making API requests, make sure they're pointed to our sandbox base URL: https://api-sandbox.mercury.com/api/v1/"; "If you're using Sandbox for testing OAuth2 integrations, the base URL is https://oauth2-sandbox.mercury.com/"; the sandbox home page comes "pre-loaded with dummy data including organizations, accounts, transactions, and account balances to allow testing", and "Tokens created outside of the sandbox (like in production) won't work here."”
• [probe] https://github.com/MercuryTechnologies/mercury-cli“PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The official command-line interface for Mercury.'). Installed via the documented installer `curl -sSf https://cli.mercury.com/install.sh | sh` (HTTP 200) → downloaded mercury_0.11.8_macos_arm64.zip, verified checksum, installed binary. Ran `mercury --version` → "mercury version 0.11.8" (exit 0). Ran `mercury --help` → full command tree: Auth (login/logout/status), Onboarding (apply), Resources (accounts, cards, categories, credit, customers, events, invoices, org, payments, recipients, safes, statements, transactions, treasury, users, webhooks), Utility (upgrade), plus --format/--api-key/--environment flags (sandbox|production). No authentication or account access was performed.”

Rely on versioned APIs with a documented deprecation policyweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

• [claimed-docs] https://docs.mercury.com/reference“API base paths are versioned under /api/v1/ ("get https://api.mercury.com/api/v1/account/{accountId}/cards") and the docs hub nav publishes a documentation version picker with three versions (v1-pre, v1, v2) alongside Guides / Recipes / API Reference / Changelog. (No written deprecation/sunset policy page is published anywhere on docs.mercury.com.)”
• [claimed-docs] https://docs.mercury.com/changelog/credit-statement-endpoint-updated-balance-and-transaction-behavior.md“Mercury publishes a public API changelog (docs.mercury.com/changelog) with dated change notices and migration guidance, e.g. "Credit Statement Endpoint: Updated balance and transaction behavior" — "This applies to statements generated after June 15, 2026; statements generated on or before that date are unaffected" — with a "Migration Guide" section: "Integrations that parse the transaction list to identify autopay, or that assume charges/payments use the previous sign convention, should be updated to reflect the changes above."”
• [claimed-docs] https://docs.mercury.com/reference“Every endpoint page on the API Reference hub (docs.mercury.com/reference, ReadMe) embeds a live request runner and generated code samples: "Click `Try It!` to start a request and see the response here! Or choose an example:", with a Language picker (Shell, Node, Ruby, PHP, Python), a Bearer credentials field, per-endpoint path/query params, and 200/404 response schemas — e.g. "get https://api.mercury.com/api/v1/account/{accountId}/cards".”

Do everything through the API that I can do in the UIweight 2

2 (weight) × 7 (quality) × 0.6 (partial) = 8.4 of 20 max

• [claimed-docs] https://mercury.com“AI reads bills, populates details automatically, and remembers past recipients — so you can approve and pay in seconds.”
• [claimed-docs] https://docs.mercury.com“Mercury API endpoint catalog: List all transactions, Get a transaction by ID, Update transaction metadata, Upload a transaction attachment; Categories: List/Create/Edit/Delete a category; Statements: Download account statement PDF; Merchants: List merchants; Treasury: Get treasury transactions, Get treasury account statements.”
• [claimed-docs] https://docs.mercury.com“Accounts Receivable API: Customers (List/Create/Get/Update/Delete a customer); Invoices (List/Create/Get/Update/Cancel an invoice, Download invoice PDF); Webhooks (Create/Update/Verify/Get/Delete webhook endpoints); Events (Get all events, Get event by ID).”
• [claimed-docs] https://mercury.com/api“Write actions such as making payments, categorizing transactions, creating invoices, and uploading receipts”
• [claimed-docs] https://docs.mercury.com/changelog/cards-api-now-available.md“You can now issue virtual cards, manage spending limits, and control card lifecycle states — all through the API.”
• [claimed-docs] https://docs.mercury.com/changelog/vault-api-retrieve-agent-card-credentials.md“Agents can now pull full card credentials - number, expiry, and CVC - for agent cards through the new Vault API”
• [probe] https://github.com/MercuryTechnologies/mercury-cli“PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The official command-line interface for Mercury.'). Installed via the documented installer `curl -sSf https://cli.mercury.com/install.sh | sh` (HTTP 200) → downloaded mercury_0.11.8_macos_arm64.zip, verified checksum, installed binary. Ran `mercury --version` → "mercury version 0.11.8" (exit 0). Ran `mercury --help` → full command tree: Auth (login/logout/status), Onboarding (apply), Resources (accounts, cards, categories, credit, customers, events, invoices, org, payments, recipients, safes, statements, transactions, treasury, users, webhooks), Utility (upgrade), plus --format/--api-key/--environment flags (sandbox|production). No authentication or account access was performed.”
• [probe] https://docs.mercury.com/docs/supported-tools-on-mercury-mcp.md“PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getAccount, getAccountCards, getAccountStatements, getTransaction, getAccounts, listCategories, listCredit, getOrganization, getRecipient, getRecipients, listTransactions, getTreasury, getTreasuryTransactions, getCard, listCards, getUser, getUsers, getWebhook, getWebhooks, getTransactionById, getTreasuryStatements, listSendMoneyApprovalRequests, getSafeRequest, getSafeRequests, listRecipientsAttachments, getAttachment, getCustomer, listCustomers, getInvoice, listInvoices, listInvoiceAttachments. Consistent with docs stating the hosted MCP has 'read-only access to certain types of information.'”
• [probe] https://mcp.mercury.com/mcp“PROBE mcp-runtime: Mercury's MCP is a remote, hosted, streamable-HTTP server (per docs, no stdio/npx variant exists — "Mercury does not offer a non-hosted MCP at this time"). Unauthenticated JSON-RPC `initialize` POST to https://mcp.mercury.com/mcp → HTTP 401 with header `www-authenticate: Bearer error="invalid_token", error_description="Missing Authorization header"` (served via Cloudflare/Express). GET https://mcp.mercury.com/.well-known/oauth-protected-resource → 200 `{"resource":"https://mcp.mercury.com/mcp","authorization_servers":["https://mcp.mercury.com/"],"scopes_supported":["read","offline_access"]}`. GET https://mcp.mercury.com/.well-known/oauth-authorization-server → 200, confirms RFC 7591 dynamic client registration endpoints (register/authorize/token) with PKCE S256 required. Confirms a live, OAuth-gated, read-only remote MCP server; no unauthenticated tool listing is possible by design. No real account was authenticated against.”

Export all of my data in open formats and leaveweight 3

3 (weight) × 5 (quality) × 0.6 (partial) = 9.0 of 30 max

• [claimed-docs] https://docs.mercury.com“Mercury API endpoint catalog: List all transactions, Get a transaction by ID, Update transaction metadata, Upload a transaction attachment; Categories: List/Create/Edit/Delete a category; Statements: Download account statement PDF; Merchants: List merchants; Treasury: Get treasury transactions, Get treasury account statements.”
• [claimed-docs] https://mercury.com/api“Pull balances, list transactions, and initiate ACH transfers — all through a single REST API”
• [probe] https://github.com/MercuryTechnologies/mercury-cli“PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The official command-line interface for Mercury.'). Installed via the documented installer `curl -sSf https://cli.mercury.com/install.sh | sh` (HTTP 200) → downloaded mercury_0.11.8_macos_arm64.zip, verified checksum, installed binary. Ran `mercury --version` → "mercury version 0.11.8" (exit 0). Ran `mercury --help` → full command tree: Auth (login/logout/status), Onboarding (apply), Resources (accounts, cards, categories, credit, customers, events, invoices, org, payments, recipients, safes, statements, transactions, treasury, users, webhooks), Utility (upgrade), plus --format/--api-key/--environment flags (sandbox|production). No authentication or account access was performed.”
• [claimed-docs] https://docs.mercury.com/docs/using-mercury-sandbox.md“Docs, "Using the Mercury Sandbox for Testing": sign up for a sandbox account at https://sandbox.mercury.com/signup; "When making API requests, make sure they're pointed to our sandbox base URL: https://api-sandbox.mercury.com/api/v1/"; "If you're using Sandbox for testing OAuth2 integrations, the base URL is https://oauth2-sandbox.mercury.com/"; the sandbox home page comes "pre-loaded with dummy data including organizations, accounts, transactions, and account balances to allow testing", and "Tokens created outside of the sandbox (like in production) won't work here."”

Read the product's source under an open licenseweight 2

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Self-host the core productweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Get AI-generated insights and suggestions from my data inside the productweight 2

2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max

• [claimed-docs] https://mercury.com“AI reads bills, populates details automatically, and remembers past recipients — so you can approve and pay in seconds.”
• [claimed-docs] https://mercury.com“Sync with Quickbooks, Xero or NetSuite, and save hours with AI-powered automations to close your books faster.”
• [claimed-docs] https://mercury.com“Email or upload receipts and we’ll auto-attach them to the right card transaction. You don’t lift a finger.”
• [probe] https://docs.mercury.com/docs/supported-tools-on-mercury-mcp.md“PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getAccount, getAccountCards, getAccountStatements, getTransaction, getAccounts, listCategories, listCredit, getOrganization, getRecipient, getRecipients, listTransactions, getTreasury, getTreasuryTransactions, getCard, listCards, getUser, getUsers, getWebhook, getWebhooks, getTransactionById, getTreasuryStatements, listSendMoneyApprovalRequests, getSafeRequest, getSafeRequests, listRecipientsAttachments, getAttachment, getCustomer, listCustomers, getInvoice, listInvoices, listInvoiceAttachments. Consistent with docs stating the hosted MCP has 'read-only access to certain types of information.'”
• [claimed-docs] https://github.com/MercuryTechnologies/mercury-skills“Official MercuryTechnologies/mercury-skills repo, "Mercury Skills Directory": "Agent skills that drive the Mercury CLI. Each skill is a self-contained SKILL.md following the Agent Skills format" — installable via `npx skills add git@github.com:MercuryTechnologies/mercury-skills.git`, with skills like mercury-analyze-spend, mercury-detect-anomaly, and mercury-receipt-upload; "The CLI handles auth itself: set MERCURY_API_KEY in your environment, or run mercury login".”
• [claimed-docs] https://docs.mercury.com/docs/supported-tools-on-mercury-mcp.md“you can ask natural language questions like \`What's my balance today?\` and \`Graph my last 6 months of transactions\`”

Set up automations that run autonomously in the backgroundweight 2

2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max

• [claimed-docs] https://mercury.com“AI reads bills, populates details automatically, and remembers past recipients — so you can approve and pay in seconds.”
• [claimed-docs] https://mercury.com“Send manual and automatic invoices, accept flexible payment methods, and manage customer details right from your Mercury account.”
• [claimed-docs] https://mercury.com“Sync with Quickbooks, Xero or NetSuite, and save hours with AI-powered automations to close your books faster.”
• [claimed-docs] https://mercury.com/api“Run Mercury operations from your terminal, a script, or a CI pipeline”
• [claimed-docs] https://mercury.com/api“Write actions such as making payments, categorizing transactions, creating invoices, and uploading receipts”
• [probe] https://docs.mercury.com/docs/supported-tools-on-mercury-mcp.md“PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getAccount, getAccountCards, getAccountStatements, getTransaction, getAccounts, listCategories, listCredit, getOrganization, getRecipient, getRecipients, listTransactions, getTreasury, getTreasuryTransactions, getCard, listCards, getUser, getUsers, getWebhook, getWebhooks, getTransactionById, getTreasuryStatements, listSendMoneyApprovalRequests, getSafeRequest, getSafeRequests, listRecipientsAttachments, getAttachment, getCustomer, listCustomers, getInvoice, listInvoices, listInvoiceAttachments. Consistent with docs stating the hosted MCP has 'read-only access to certain types of information.'”
• [claimed-docs] https://github.com/MercuryTechnologies/mercury-skills“Official MercuryTechnologies/mercury-skills repo, "Mercury Skills Directory": "Agent skills that drive the Mercury CLI. Each skill is a self-contained SKILL.md following the Agent Skills format" — installable via `npx skills add git@github.com:MercuryTechnologies/mercury-skills.git`, with skills like mercury-analyze-spend, mercury-detect-anomaly, and mercury-receipt-upload; "The CLI handles auth itself: set MERCURY_API_KEY in your environment, or run mercury login".”
• [probe] https://mcp.mercury.com/mcp“PROBE mcp-runtime: Mercury's MCP is a remote, hosted, streamable-HTTP server (per docs, no stdio/npx variant exists — "Mercury does not offer a non-hosted MCP at this time"). Unauthenticated JSON-RPC `initialize` POST to https://mcp.mercury.com/mcp → HTTP 401 with header `www-authenticate: Bearer error="invalid_token", error_description="Missing Authorization header"` (served via Cloudflare/Express). GET https://mcp.mercury.com/.well-known/oauth-protected-resource → 200 `{"resource":"https://mcp.mercury.com/mcp","authorization_servers":["https://mcp.mercury.com/"],"scopes_supported":["read","offline_access"]}`. GET https://mcp.mercury.com/.well-known/oauth-authorization-server → 200, confirms RFC 7591 dynamic client registration endpoints (register/authorize/token) with PKCE S256 required. Confirms a live, OAuth-gated, read-only remote MCP server; no unauthenticated tool listing is possible by design. No real account was authenticated against.”

Delegate tasks to a built-in AI assistant inside the productweight 3

3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max

• [claimed-docs] https://mercury.com“AI reads bills, populates details automatically, and remembers past recipients — so you can approve and pay in seconds.”
• [claimed-docs] https://mercury.com“Sync with Quickbooks, Xero or NetSuite, and save hours with AI-powered automations to close your books faster.”
• [probe] https://mcp.mercury.com/mcp“PROBE mcp-runtime: Mercury's MCP is a remote, hosted, streamable-HTTP server (per docs, no stdio/npx variant exists — "Mercury does not offer a non-hosted MCP at this time"). Unauthenticated JSON-RPC `initialize` POST to https://mcp.mercury.com/mcp → HTTP 401 with header `www-authenticate: Bearer error="invalid_token", error_description="Missing Authorization header"` (served via Cloudflare/Express). GET https://mcp.mercury.com/.well-known/oauth-protected-resource → 200 `{"resource":"https://mcp.mercury.com/mcp","authorization_servers":["https://mcp.mercury.com/"],"scopes_supported":["read","offline_access"]}`. GET https://mcp.mercury.com/.well-known/oauth-authorization-server → 200, confirms RFC 7591 dynamic client registration endpoints (register/authorize/token) with PKCE S256 required. Confirms a live, OAuth-gated, read-only remote MCP server; no unauthenticated tool listing is possible by design. No real account was authenticated against.”
• [probe] https://docs.mercury.com/docs/supported-tools-on-mercury-mcp.md“PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getAccount, getAccountCards, getAccountStatements, getTransaction, getAccounts, listCategories, listCredit, getOrganization, getRecipient, getRecipients, listTransactions, getTreasury, getTreasuryTransactions, getCard, listCards, getUser, getUsers, getWebhook, getWebhooks, getTransactionById, getTreasuryStatements, listSendMoneyApprovalRequests, getSafeRequest, getSafeRequests, listRecipientsAttachments, getAttachment, getCustomer, listCustomers, getInvoice, listInvoices, listInvoiceAttachments. Consistent with docs stating the hosted MCP has 'read-only access to certain types of information.'”

Operate the product with natural-language commandsweight 2

2 (weight) × 7 (quality) × 0.6 (partial) = 8.4 of 20 max

• [claimed-docs] https://docs.mercury.com/docs/supported-tools-on-mercury-mcp.md“What's my balance today?”
• [claimed-docs] https://docs.mercury.com/docs/supported-tools-on-mercury-mcp.md“you can ask natural language questions like \`What's my balance today?\` and \`Graph my last 6 months of transactions\`”
• [claimed-docs] https://mercury.com/api“Give your agents the same financial context you have — no code required”
• [claimed-docs] https://mercury.com/api“Query balances, transaction history, and account data in natural language”
• [probe] https://mcp.mercury.com/mcp“PROBE mcp-runtime: Mercury's MCP is a remote, hosted, streamable-HTTP server (per docs, no stdio/npx variant exists — "Mercury does not offer a non-hosted MCP at this time"). Unauthenticated JSON-RPC `initialize` POST to https://mcp.mercury.com/mcp → HTTP 401 with header `www-authenticate: Bearer error="invalid_token", error_description="Missing Authorization header"` (served via Cloudflare/Express). GET https://mcp.mercury.com/.well-known/oauth-protected-resource → 200 `{"resource":"https://mcp.mercury.com/mcp","authorization_servers":["https://mcp.mercury.com/"],"scopes_supported":["read","offline_access"]}`. GET https://mcp.mercury.com/.well-known/oauth-authorization-server → 200, confirms RFC 7591 dynamic client registration endpoints (register/authorize/token) with PKCE S256 required. Confirms a live, OAuth-gated, read-only remote MCP server; no unauthenticated tool listing is possible by design. No real account was authenticated against.”
• [probe] https://docs.mercury.com/docs/supported-tools-on-mercury-mcp.md“PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getAccount, getAccountCards, getAccountStatements, getTransaction, getAccounts, listCategories, listCredit, getOrganization, getRecipient, getRecipients, listTransactions, getTreasury, getTreasuryTransactions, getCard, listCards, getUser, getUsers, getWebhook, getWebhooks, getTransactionById, getTreasuryStatements, listSendMoneyApprovalRequests, getSafeRequest, getSafeRequests, listRecipientsAttachments, getAttachment, getCustomer, listCustomers, getInvoice, listInvoices, listInvoiceAttachments. Consistent with docs stating the hosted MCP has 'read-only access to certain types of information.'”

Perform bulk operations across many items at onceweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

• [claimed-docs] https://mercury.com“Instantly spin up as many virtual cards as you need. Create cards for any purpose — ad spend, contractors, you name it.”
• [claimed-docs] https://mercury.com/api“Create up to 500 invoices/month on Mercury Plus, or unlimited invoices with Pro”
• [community] https://news.ycombinator.com/item?id=47991802“5-year Mercury customer: wire transfers never disappear, created hundreds of virtual debit cards with individual limits, dozens of purpose-named accounts with auto-funding rules, and shared login access with ex-wife. Only annoyance was when Mercury canceled all existing virtual cards at once, disrupting recurring billing.”
• [probe] https://github.com/MercuryTechnologies/mercury-cli“PROBE official-cli: github.com/MercuryTechnologies/mercury-cli (Mercury's own GitHub org, 171 stars, last push 2026-08-12, README: 'The official command-line interface for Mercury.'). Installed via the documented installer `curl -sSf https://cli.mercury.com/install.sh | sh` (HTTP 200) → downloaded mercury_0.11.8_macos_arm64.zip, verified checksum, installed binary. Ran `mercury --version` → "mercury version 0.11.8" (exit 0). Ran `mercury --help` → full command tree: Auth (login/logout/status), Onboarding (apply), Resources (accounts, cards, categories, credit, customers, events, invoices, org, payments, recipients, safes, statements, transactions, treasury, users, webhooks), Utility (upgrade), plus --format/--api-key/--environment flags (sandbox|production). No authentication or account access was performed.”
• [probe] https://docs.mercury.com/docs/supported-tools-on-mercury-mcp.md“PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getAccount, getAccountCards, getAccountStatements, getTransaction, getAccounts, listCategories, listCredit, getOrganization, getRecipient, getRecipients, listTransactions, getTreasury, getTreasuryTransactions, getCard, listCards, getUser, getUsers, getWebhook, getWebhooks, getTransactionById, getTreasuryStatements, listSendMoneyApprovalRequests, getSafeRequest, getSafeRequests, listRecipientsAttachments, getAttachment, getCustomer, listCustomers, getInvoice, listInvoices, listInvoiceAttachments. Consistent with docs stating the hosted MCP has 'read-only access to certain types of information.'”
• [claimed-docs] https://docs.mercury.com“Accounts Receivable API: Customers (List/Create/Get/Update/Delete a customer); Invoices (List/Create/Get/Update/Cancel an invoice, Download invoice PDF); Webhooks (Create/Update/Verify/Get/Delete webhook endpoints); Events (Get all events, Get event by ID).”

Define rules that trigger actions automatically on eventsweight 3

3 (weight) × 5 (quality) × 0.6 (partial) = 9.0 of 30 max

• [claimed-docs] https://docs.mercury.com“Accounts Receivable API: Customers (List/Create/Get/Update/Delete a customer); Invoices (List/Create/Get/Update/Cancel an invoice, Download invoice PDF); Webhooks (Create/Update/Verify/Get/Delete webhook endpoints); Events (Get all events, Get event by ID).”
• [claimed-docs] https://mercury.com“Sync with Quickbooks, Xero or NetSuite, and save hours with AI-powered automations to close your books faster.”
• [claimed-docs] https://mercury.com“Email or upload receipts and we’ll auto-attach them to the right card transaction. You don’t lift a finger.”
• [claimed-docs] https://mercury.com“Earn unlimited cashback automatically deposited into your account — no manual redemption or confusing points.”
• [probe] https://docs.mercury.com/docs/supported-tools-on-mercury-mcp.md“PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getAccount, getAccountCards, getAccountStatements, getTransaction, getAccounts, listCategories, listCredit, getOrganization, getRecipient, getRecipients, listTransactions, getTreasury, getTreasuryTransactions, getCard, listCards, getUser, getUsers, getWebhook, getWebhooks, getTransactionById, getTreasuryStatements, listSendMoneyApprovalRequests, getSafeRequest, getSafeRequests, listRecipientsAttachments, getAttachment, getCustomer, listCustomers, getInvoice, listInvoices, listInvoiceAttachments. Consistent with docs stating the hosted MCP has 'read-only access to certain types of information.'”

Schedule recurring jobs or workflowsweight 2

2 (weight) × 3 (quality) × 0.6 (partial) = 3.6 of 20 max

• [claimed-docs] https://mercury.com“Send manual and automatic invoices, accept flexible payment methods, and manage customer details right from your Mercury account.”
• [claimed-docs] https://mercury.com“Sync with Quickbooks, Xero or NetSuite, and save hours with AI-powered automations to close your books faster.”
• [claimed-docs] https://mercury.com“AI reads bills, populates details automatically, and remembers past recipients — so you can approve and pay in seconds.”
• [community] https://news.ycombinator.com/item?id=47991802“5-year Mercury customer: wire transfers never disappear, created hundreds of virtual debit cards with individual limits, dozens of purpose-named accounts with auto-funding rules, and shared login access with ex-wife. Only annoyance was when Mercury canceled all existing virtual cards at once, disrupting recurring billing.”
• [probe] https://docs.mercury.com/docs/supported-tools-on-mercury-mcp.md“PROBE mcp-tool-inventory: documented Mercury MCP tool list totals 31 tools, all read-only (get*/list*, zero write/send/create actions): getAccount, getAccountCards, getAccountStatements, getTransaction, getAccounts, listCategories, listCredit, getOrganization, getRecipient, getRecipients, listTransactions, getTreasury, getTreasuryTransactions, getCard, listCards, getUser, getUsers, getWebhook, getWebhooks, getTransactionById, getTreasuryStatements, listSendMoneyApprovalRequests, getSafeRequest, getSafeRequests, listRecipientsAttachments, getAttachment, getCustomer, listCustomers, getInvoice, listInvoices, listInvoiceAttachments. Consistent with docs stating the hosted MCP has 'read-only access to certain types of information.'”

Version, review, and roll back my automationsweight 1

1 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 10 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh