{ "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-27", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.6", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "tool": { "slug": "financial-cents-mcp", "name": "Financial Cents MCP", "vendor": "Financial Cents LLC", "vendorUrl": "https://financial-cents.com", "kind": "mcp", "category": "project-management", "summary": "Financial Cents MCP is a hosted MCP server from Financial Cents LLC that lets AI assistants read and update an accounting firm's practice data, including clients, projects, tasks, time, invoices, proposals and client chat.", "url": "https://www.anchorterminal.com/tools/financial-cents-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/financial-cents-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/financial-cents-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/financial-cents-mcp.json", "license": "Proprietary hosted service under Financial Cents' terms of use, which are hosted on iubenda and weren't read because iubenda's robots.txt disallows them. No source is public", "transports": [ "streamable-http" ], "remoteUrl": "https://app.financial-cents.com/mcp", "packages": [], "auth": "oauth", "authNotes": "OAuth only, with no API key. The protected-resource metadata names one scope, `mcp:use`, and the authorisation server gives the authorisation code grant with PKCE S256, refresh tokens and dynamic client registration; no revocation endpoint is advertised. The person signs in on app.financial-cents.com and picks one firm on the consent screen, and the token stays bound to it. Every call runs through the user's own app permissions, so rates and billing data need the matching permissions. Connections are listed and revoked in Settings, API, FC MCP. Cloud-hosted clients need their callback approved by Financial Cents; Claude, ChatGPT, Grok, Cursor's web agents, VS Code for the Web, Perplexity, Notion, Gumloop and Viktor are approved (https://app.financial-cents.com/.well-known/oauth-protected-resource/mcp, https://app.financial-cents.com/.well-known/oauth-authorization-server, https://app.financial-cents.com/mcp-guide, checked 2026-10-27).", "pricing": "paid", "pricingNotes": "Included in the Scale plan, $69 a user a month billed annually or $89 a user a month billed monthly with at least 5 users, all on 12-month agreements. Team ($49) and Solo ($19) don't include it, and Enterprise is by sales. A 14-day trial needs no card; whether the MCP is on during the trial isn't stated, and the MCP page says support may need to enable it for a firm. The pricing page has no MCP row. Month-End Close is an add-on at $5 a client a month (https://financial-cents.com/pricing/, https://financial-cents.com/mcp/, checked 2026-10-27).", "priceSummary": "$69 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the MCP page, the setup guide, the pricing page or the release. Unauthenticated MCP calls answer 401 with an OAuth resource-metadata pointer, not a payment request (checked 2026-10-27).", "endpoints": [] }, "toolCount": 40, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-27" }, "docsUrl": "https://app.financial-cents.com/mcp-guide", "capabilities": [ "tasks.create", "tasks.update", "projects.manage", "projects.reporting", "crm.records", "accounting.invoices" ], "tags": [ "official", "hosted", "mcp", "closed-source", "oauth", "paid", "free-trial", "no-card", "no-status-page", "soc2", "new" ], "lastRelease": "2026-10-05", "graded": true, "anchor": { "graded": true, "score": 39.7, "grade": "E", "agentReady": false, "rank": 1093, "ranked": true, "rankOf": 1212, "categoryRank": 15, "methodology": "0.6", "run": "2026-10-01", "scores": { "ergonomics": 48, "maintenance": 50, "payments": 25, "reliability": 23, "schema": 40, "security": 61, "transparency": 53 }, "pending": [ "performance", "tasks" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 23, "points": 4.6, "reason": "Graded with the hosted lines, on the remote MCP server. No status page was found (status.financial-cents.com doesn't resolve) (0 of 20), so there's no readable incident history (5 of 30). Financial Cents says MCP requests are rate limited but gives no number; the REST API's 250 requests a minute is for a separate surface (0 of 15). No 429 or Retry-After guidance, but the tool descriptions give safe-retry rules for writes. Don't retry a successful send or charge, send `expected_amount_remaining` so a credit-memo retry can't apply twice, and upload IDs are single use (8 of 15). No SLA found in the pages we could read; the terms weren't readable (0 of 10). The changelog calls it an initial release and nothing labels it beta (10 of 10). Total 23.", "checked": "2026-10-27" }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 40, "points": 6.5, "reason": "No machine-readable contract could be read. `tools/list` answers 401 without a signed-in Scale account and no public manifest or schema exists (0 of 25). No llms.txt on either host and no Markdown docs for the MCP; the gitbook llms.txt covers the REST API only (0 of 10). Every tool's full description is public on the setup guide, and they say what each tool is for, which tool to use instead, what it won't do and the units of money fields (18 of 20). The descriptions name enums such as `resource`, `board`, `group_by` and `log_type` and the required fields on create, but the typed schemas weren't read (6 of 15). Example prompts mapped to tools, a troubleshooting section, and descriptions that say which inputs are rejected and why; no error shape (8 of 15). A public changelog with a dated entry for the initial release, but no server version (8 of 15). Total 40.", "checked": "2026-10-27" }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 48, "points": 7.8, "reason": "Graded on the MCP server. 40 tools, more than 30, with about 30,000 characters of descriptions on the guide, the longest about 2,100, before schemas. No toolsets or read-only subset (5 of 25). List tools take filters, `limit`, pagination, `include` for nested data and `group_by`, with totals over the whole filtered set (18 of 20). Descriptions say what gets rejected and that the reason is returned, such as a locked time entry or a proposal reminder sent too soon with the next allowed time; no error codes documented (10 of 20). No idempotency keys, but `preview` on proposal sends, `expected_amount_remaining` on credit memos and single-use upload IDs. The guide labels tools Read or Write, but readOnlyHint and destructiveHint couldn't be checked (8 of 20). Omitted fields are left unchanged on updates and `whoami` grounds dates; no official SDK (7 of 15). Total 48.", "checked": "2026-10-27" }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 61, "points": 10.68, "reason": "OAuth 2.1 with PKCE S256 and dynamic client registration, tokens bound to one firm and revocable in the app, with no API key. One scope, `mcp:use`, covers every read and write, so 22 rather than 30 (22 of 30). No read-only mode. The user's app permissions apply and no tool deletes, but the server can send, charge and void invoices and email clients. Server-side flags exist only for uploads that email portal contacts (`confirm_notify`) and recurring back-charges (`confirm_back_charges`); other confirmations are left to the AI client, guided by the descriptions (10 of 20). Client-written chat and topic names come back inside `\u003cuntrusted\u003e` tags, with injection guidance on both pages (13 of 15). Financial Cents says every call is logged with who, what and how long, and connected clients are listed in Settings; no customer view of the call log is described (8 of 15). No security.txt (404 on both hosts) and no bug bounty found. The security page claims SOC II Type I and twice-yearly third-party assessments, with an attestation letter on request (8 of 20). Total 61.", "checked": "2026-10-27" }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 25, "points": 3.13, "reason": "No x402, MPP or L402 (0 of 40). Scale plan prices are public, $69 a user a month annually or $89 monthly, but the MCP has no price of its own and no row on the pricing page, so plan-only pricing (10 of 20). A 14-day trial with no card. Judgement call, 15 of 20, because the release points new firms to the trial but no page says the MCP is on during it, and the MCP page says support may need to enable it (15 of 20). A person has to sign up and sign in through a browser (0 of 20). Total 25.", "checked": "2026-10-27" }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 50, "points": 4.38, "reason": "Closed hosted service. The changelog dates the initial release to 5 October 2026, 22 days ago (30 of 30). One dated MCP entry in 90 days; the tool count grew from 33 in the recap of 19 October to 40 now, without dated notes (10 of 20). A public changelog, roadmap and feedback board on Canny, an Intercom help centre with an MCP article updated 23 October, and a Facebook community (10 of 15). Not in the official MCP registry (searches for financial-cents and financialcents returned nothing on 27 October 2026) and no SDK (0 of 15). No package (0 of 10). The server is about three weeks old. Total 50.", "checked": "2026-10-27" }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 53, "points": 4.64, "note": "editorial 30, provenance 76", "reason": "The editorial half. A closed service whose terms sit on iubenda behind a robots.txt disallow, so they weren't read (10 of 30). The privacy page shows a 2018 website policy and links an iubenda policy that wasn't readable. The security page says deleted records are removed within six months and vault records at once. Nothing was found on how MCP call logs or assistant data are kept (10 of 30). No deprecation policy or dated notices; the REST API docs warn breaking changes could happen (0 of 20). The security page names DigitalOcean and AWS with servers in New York City and Virginia, and the privacy page names Google Analytics; no full subprocessor list (10 of 20). Total 30.", "checked": "2026-10-27" } ], "assessment": { "date": "2026-10-27", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "Graded on the MCP server. 40 tools, more than 30, with about 30,000 characters of descriptions on the guide, the longest about 2,100, before schemas. No toolsets or read-only subset (5 of 25). List tools take filters, `limit`, pagination, `include` for nested data and `group_by`, with totals over the whole filtered set (18 of 20). Descriptions say what gets rejected and that the reason is returned, such as a locked time entry or a proposal reminder sent too soon with the next allowed time; no error codes documented (10 of 20). No idempotency keys, but `preview` on proposal sends, `expected_amount_remaining` on credit memos and single-use upload IDs. The guide labels tools Read or Write, but readOnlyHint and destructiveHint couldn't be checked (8 of 20). Omitted fields are left unchanged on updates and `whoami` grounds dates; no official SDK (7 of 15). Total 48.", "maintenance": "Closed hosted service. The changelog dates the initial release to 5 October 2026, 22 days ago (30 of 30). One dated MCP entry in 90 days; the tool count grew from 33 in the recap of 19 October to 40 now, without dated notes (10 of 20). A public changelog, roadmap and feedback board on Canny, an Intercom help centre with an MCP article updated 23 October, and a Facebook community (10 of 15). Not in the official MCP registry (searches for financial-cents and financialcents returned nothing on 27 October 2026) and no SDK (0 of 15). No package (0 of 10). The server is about three weeks old. Total 50.", "payments": "No x402, MPP or L402 (0 of 40). Scale plan prices are public, $69 a user a month annually or $89 monthly, but the MCP has no price of its own and no row on the pricing page, so plan-only pricing (10 of 20). A 14-day trial with no card. Judgement call, 15 of 20, because the release points new firms to the trial but no page says the MCP is on during it, and the MCP page says support may need to enable it (15 of 20). A person has to sign up and sign in through a browser (0 of 20). Total 25.", "reliability": "Graded with the hosted lines, on the remote MCP server. No status page was found (status.financial-cents.com doesn't resolve) (0 of 20), so there's no readable incident history (5 of 30). Financial Cents says MCP requests are rate limited but gives no number; the REST API's 250 requests a minute is for a separate surface (0 of 15). No 429 or Retry-After guidance, but the tool descriptions give safe-retry rules for writes. Don't retry a successful send or charge, send `expected_amount_remaining` so a credit-memo retry can't apply twice, and upload IDs are single use (8 of 15). No SLA found in the pages we could read; the terms weren't readable (0 of 10). The changelog calls it an initial release and nothing labels it beta (10 of 10). Total 23.", "schema": "No machine-readable contract could be read. `tools/list` answers 401 without a signed-in Scale account and no public manifest or schema exists (0 of 25). No llms.txt on either host and no Markdown docs for the MCP; the gitbook llms.txt covers the REST API only (0 of 10). Every tool's full description is public on the setup guide, and they say what each tool is for, which tool to use instead, what it won't do and the units of money fields (18 of 20). The descriptions name enums such as `resource`, `board`, `group_by` and `log_type` and the required fields on create, but the typed schemas weren't read (6 of 15). Example prompts mapped to tools, a troubleshooting section, and descriptions that say which inputs are rejected and why; no error shape (8 of 15). A public changelog with a dated entry for the initial release, but no server version (8 of 15). Total 40.", "security": "OAuth 2.1 with PKCE S256 and dynamic client registration, tokens bound to one firm and revocable in the app, with no API key. One scope, `mcp:use`, covers every read and write, so 22 rather than 30 (22 of 30). No read-only mode. The user's app permissions apply and no tool deletes, but the server can send, charge and void invoices and email clients. Server-side flags exist only for uploads that email portal contacts (`confirm_notify`) and recurring back-charges (`confirm_back_charges`); other confirmations are left to the AI client, guided by the descriptions (10 of 20). Client-written chat and topic names come back inside `\u003cuntrusted\u003e` tags, with injection guidance on both pages (13 of 15). Financial Cents says every call is logged with who, what and how long, and connected clients are listed in Settings; no customer view of the call log is described (8 of 15). No security.txt (404 on both hosts) and no bug bounty found. The security page claims SOC II Type I and twice-yearly third-party assessments, with an attestation letter on request (8 of 20). Total 61.", "transparency": "The editorial half. A closed service whose terms sit on iubenda behind a robots.txt disallow, so they weren't read (10 of 30). The privacy page shows a 2018 website policy and links an iubenda policy that wasn't readable. The security page says deleted records are removed within six months and vault records at once. Nothing was found on how MCP call logs or assistant data are kept (10 of 30). No deprecation policy or dated notices; the REST API docs warn breaking changes could happen (0 of 20). The security page names DigitalOcean and AWS with servers in New York City and Virginia, and the privacy page names Google Analytics; no full subprocessor list (10 of 20). Total 30." }, "sources": [ { "what": "robots.txt (financial-cents.com, app.financial-cents.com, help.financial-cents.com, financial-cents.canny.io, www.iubenda.com)", "url": "https://financial-cents.com/robots.txt", "seen": "2026-10-27" }, { "what": "MCP page", "url": "https://financial-cents.com/mcp/", "seen": "2026-10-27" }, { "what": "MCP setup guide and tool list", "url": "https://app.financial-cents.com/mcp-guide", "seen": "2026-10-27" }, { "what": "launch release, 20 October 2026", "url": "https://financial-cents.com/resources/articles/financial-cents-launches-mcp-server/", "seen": "2026-10-27" }, { "what": "changelog, entry of 5 October 2026", "url": "https://financial-cents.canny.io/changelog", "seen": "2026-10-27" }, { "what": "September 2026 recap", "url": "https://financial-cents.com/resources/articles/whats-new-at-financial-cents-september-2026/", "seen": "2026-10-27" }, { "what": "help centre article on connecting assistants", "url": "https://help.financial-cents.com/en/articles/17713340-connect-your-ai-assistant-to-financial-cents", "seen": "2026-10-27" }, { "what": "pricing", "url": "https://financial-cents.com/pricing/", "seen": "2026-10-27" }, { "what": "security page", "url": "https://financial-cents.com/security/", "seen": "2026-10-27" }, { "what": "privacy policy page", "url": "https://financial-cents.com/privacy-policy/", "seen": "2026-10-27" }, { "what": "terms of use page (iubenda embed, not read)", "url": "https://financial-cents.com/terms-of-use/", "seen": "2026-10-27" }, { "what": "MCP initialize and tools/list without a token (401)", "url": "https://app.financial-cents.com/mcp", "seen": "2026-10-27" }, { "what": "OAuth protected-resource metadata", "url": "https://app.financial-cents.com/.well-known/oauth-protected-resource/mcp", "seen": "2026-10-27" }, { "what": "OAuth authorisation server metadata", "url": "https://app.financial-cents.com/.well-known/oauth-authorization-server", "seen": "2026-10-27" }, { "what": "REST API docs, rate limits and authentication", "url": "https://financial-cents.gitbook.io/public-api-documentation/reference/rate-limits.md", "seen": "2026-10-27" }, { "what": "official MCP registry search", "url": "https://registry.modelcontextprotocol.io/v0/servers?search=financial-cents", "seen": "2026-10-27" }, { "what": "RDAP for financial-cents.com", "url": "https://rdap.verisign.com/com/v1/domain/financial-cents.com", "seen": "2026-10-27" } ], "openQuestions": [ "unchecked: the tools as served, because `initialize` and `tools/list` answered 401 without a signed-in Scale account. The count of 40, the names and the descriptions are from the setup guide, which says they're read from the code; input schemas and annotations are unread.", "unchecked: the terms of use and the current privacy policy, both iubenda documents that iubenda's robots.txt disallows. The privacy page shows a 2018 website policy.", "unchecked: whether the 14-day trial includes the MCP. The release points new firms to the trial, the MCP page says support may need to enable MCP for a firm, and the pricing page has no MCP row.", "firstReleased is 5 October 2026, the date of the changelog entry for the initial release, which says it shipped \"this past week\". The September recap also places the launch in September. Both are earlier than the release of 20 October, which is the lead's date. The MCP page was last modified on 15 October per the sitemap.", "The September recap says Claude users can search for Financial Cents in their connectors, but no Financial Cents entry was found in claude.com's connector sitemap, and the setup guide uses a custom connector. Recorded, not deducted.", "The deduction for the MCP page's view-only description of invoices, payments and proposals may lapse if the page is updated to match the guide; confirm at landing.", "Category. project-management, because tasks, projects, time and client work are the server's main jobs. About a third of the tools are billing (invoices, payments, proposals, credit memos, tax codes), so accounting was the alternative, and crm.records and accounting.invoices are listed as capabilities. Judgement call.", "Our own products. Financial Cents MCP doesn't do LocalGhost's job or letme's. It reaches one vendor's practice-management data and picks no tools. Graded the normal way." ] }, "negative": -2, "negativeNotes": [ "-2, misleading claim. The MCP page and its FAQ (last modified 15 October 2026) say the server can view invoices, payments and proposals, while the setup guide lists `manage_invoice`, `invoice_actions` (send, finalise, charge, void) and `proposal_actions` (send). That understates the server's reach over client money. Checked 27 October 2026 (https://financial-cents.com/mcp/, https://app.financial-cents.com/mcp-guide)." ], "verdict": "The server gives assistants 40 tools over an accounting firm's Financial Cents data, under the user's own permissions and bound to one firm by OAuth. Tool descriptions are detailed and client chat is marked as untrusted. It can send and charge invoices with one undivided scope, and there's no status page, numeric MCP rate limit or readable tool schema.", "bestFor": "Accounting, bookkeeping and tax firms on Financial Cents Scale who want an assistant to answer workload, billing and client questions and log time or create tasks.", "strengths": [ "OAuth 2.1 with PKCE S256 and dynamic client registration, each token bound to one firm and revocable in Settings, API", "Every one of the 40 tools is named and described on a public page, with when to use it, what it won't do and units such as cents or dollars", "List tools filter, group and total across the whole filtered set, so one call answers most firm-wide questions", "Client-written chat text and topic names come back wrapped in `\u003cuntrusted\u003e` tags, and the guide warns about prompt injection", "No delete tool, and risky writes carry guards such as `preview` on proposal sends, `confirm_notify` and `expected_amount_remaining`" ], "weaknesses": [ "One OAuth scope, `mcp:use`, covers reads and every write, including sending, charging and voiding invoices", "The MCP marketing page says invoices, payments and proposals are view-only, while the guide lists tools that send, charge and void them", "No status page, SLA or numeric rate limit for the MCP; the REST API's 250 requests a minute is a separate surface", "Input schemas and annotations aren't public, since `initialize` and `tools/list` need a signed-in Scale account", "Scale plan only, at $69 a user a month billed annually; no free plan and no MCP row on the pricing page" ], "agentNotes": [ "Call `whoami` first and work out date windows from `user.timezone`, not `company.timezone`", "Resolve clients and projects with `list_clients` or `list_projects` search, since `lookup` covers only reference data such as users, tags and service items", "Check money units per tool. Invoices, payments, proposals and credit memos use integer cents, while time entries and service-item rates use dollars", "Never retry a successful `invoice_actions`, `proposal_actions` or credit-memo create, since a second call can email or charge the client again", "Get the person's approval before any write, and use `preview: true` before sending a proposal" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.6", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 39.7 } ], "editorialScores": { "ergonomics": 48, "maintenance": 50, "payments": 25, "reliability": 23, "schema": 40, "security": 61, "transparency": 30 }, "provenanceScore": 76, "checked": { "categories": { "ergonomics": "2026-10-27", "maintenance": "2026-10-27", "payments": "2026-10-27", "reliability": "2026-10-27", "schema": "2026-10-27", "security": "2026-10-27", "transparency": "2026-10-27" }, "last": "2026-10-27", "oldest": "2026-10-27", "stale": false, "staleAfterDays": 90 }, "scoreHistory": [ { "date": "2026-10-27", "grade": "E", "kind": "listed", "method": "0.6", "score": 39.7 } ] }, "connect": { "claudeCode": "claude mcp add --transport http financial-cents https://app.financial-cents.com/mcp", "config": { "mcpServers": { "financial-cents": { "url": "https://app.financial-cents.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/tasks.create", "tool": "https://letme.dev/financial-cents-mcp" }, "notable": [ "Financial Cents' release dated 20 October 2026 announces the MCP server, \"available now on the Scale plan\", for Claude, ChatGPT, Gemini and other assistants (https://financial-cents.com/resources/articles/financial-cents-launches-mcp-server/)", "The public changelog's entry of 5 October 2026 lists \"Financial Cents MCP - Initial Release\" among changes released \"this past week\", and calls it a first version. The September 2026 recap, published 19 October, also places the launch in September (https://financial-cents.canny.io/changelog, https://financial-cents.com/resources/articles/whats-new-at-financial-cents-september-2026/)", "The setup guide lists 40 tools, 22 read and 18 write (two of them file uploads), with each tool's full description, and says the list is read from the code. The September recap of 19 October gave 21 read and 12 write tools (https://app.financial-cents.com/mcp-guide)", "Write tools create and update clients, projects, sections, team tasks, time entries and timers, client chat topics and messages, service items, discounts, tax codes, credit memos, invoices and proposals. `invoice_actions` sends, finalises, charges or voids an invoice, and `proposal_actions` sends a proposal. No tool deletes (https://app.financial-cents.com/mcp-guide)", "The MCP page and its FAQ say the server can \"view\" invoices, payments, proposals and files, and doesn't mention sending, charging or voiding. The guide's tool list includes all three (https://financial-cents.com/mcp/)", "MCP `initialize` and `tools/list` sent without a token on 27 October 2026 both answered 401 with `{\"error\":\"Unauthenticated.\"}` and a `WWW-Authenticate` header pointing at the protected-resource metadata, so the served schemas weren't read (https://app.financial-cents.com/mcp)", "Client chat topic names and message bodies come back inside `\u003cuntrusted\u003e` tags, per the tool descriptions, and the guide advises treating summaries as unverified when the connector is combined with other tools (https://app.financial-cents.com/mcp-guide)", "Financial Cents says every tool call is recorded with who, what and how long it took, and that requests are rate limited. No limit is given for the MCP; the REST API's docs give 250 authenticated requests a minute per application (https://financial-cents.com/mcp/, https://financial-cents.gitbook.io/public-api-documentation/reference/rate-limits.md)", "The security page says Financial Cents is SOC II Type I certified, has third-party assessments twice a year, and hosts on DigitalOcean and AWS in New York City and Virginia. The release says \"SOC 2 certified\" (https://financial-cents.com/security/)", "File uploads take three steps, a prepared upload URL, a PUT of the raw bytes within 5 minutes and a finalising call, up to 50 MB, so the client needs shell or network access (https://app.financial-cents.com/mcp-guide)", "Financial Cents' REST API at app.financial-cents.com/api/v1, also on the Scale plan, is called beta in its docs, which warn that breaking changes could happen. It's a separate surface from the MCP server (https://financial-cents.gitbook.io/public-api-documentation/)", "Financial Cents MCP doesn't do LocalGhost's job or letme's. It reaches one vendor's practice-management data and picks no tools" ], "area": "business", "details": [ { "label": "MCP endpoint", "value": "`https://app.financial-cents.com/mcp`, Streamable HTTP. Unauthenticated `initialize` and `tools/list` answer 401 with resource metadata" }, { "label": "Tools", "value": "40 per the setup guide, 22 read and 18 write. Account and lookup 2, projects and tasks 8, clients and client chat 11, files 2, billing 13, payment methods 1, time tracking 2, tax codes 1" }, { "label": "OAuth", "value": "Authorisation code with PKCE S256, refresh tokens, dynamic client registration. One scope, `mcp:use`. No revocation endpoint advertised; revoke in Settings, API, FC MCP" }, { "label": "Firm binding", "value": "Each token is bound to the one firm picked at consent and stops working when the user's membership ends. Calls follow the user's own permissions" }, { "label": "Money-moving tools", "value": "`invoice_actions` (send, finalise, charge, void), `proposal_actions` (send, with `preview`), `manage_credit_memo` (can apply credit and mark invoices paid)" }, { "label": "Server-side checks", "value": "`confirm_notify` for uploads that email portal contacts, `confirm_back_charges` for recurring back-charges, `expected_amount_remaining` on credit-memo updates, single-use upload IDs" }, { "label": "Plan", "value": "Scale ($69 a user a month annually, $89 monthly with 5 users minimum) and Enterprise. 14-day trial, no card" }, { "label": "Clients documented", "value": "Claude, Claude Code, Cursor, VS Code, ChatGPT and Notion step by step; Zed, Windsurf, JetBrains, Warp, Raycast, LM Studio, Gemini CLI, Codex CLI, Amp, OpenCode, Cline, Gumloop, Viktor and mcp-remote briefly" }, { "label": "Status", "value": "No status page found" } ], "unitPrices": [ { "item": "Scale plan, billed annually", "unit": "seat-month", "usd": 69, "note": "Includes the MCP server and the REST API; 12-month agreement" }, { "item": "Scale plan, billed monthly", "unit": "seat-month", "usd": 89, "note": "At least 5 users; 12-month agreement" } ], "provenance": { "legalEntity": "Financial Cents LLC", "domain": "financial-cents.com", "domainRegistered": "2017-04-10", "endpointOnVendorDomain": true, "terms": "https://financial-cents.com/terms-of-use/", "privacy": "https://financial-cents.com/privacy-policy/", "statusPage": "", "changelog": "https://financial-cents.canny.io/changelog", "securityTxt": "none", "checked": "2026-10-27", "notes": [ "The setup guide's footer reads Copyright 2017-2026 Financial Cents LLC. The release is datelined Atlanta.", "The terms-of-use page embeds iubenda's terms (https://www.iubenda.com/terms-and-conditions/98813471), which iubenda's robots.txt disallows for every crawler, so they weren't read.", "The privacy-policy page shows a policy with an effective date of 5 October 2018 for the website, and links an iubenda privacy policy that robots.txt also disallows.", "/.well-known/security.txt answered 404 on financial-cents.com and app.financial-cents.com.", "No status page was found. status.financial-cents.com doesn't resolve, and the Statuspage and Instatus names for the company redirect to those vendors' home pages.", "The product changelog is on Canny, with a roadmap and feedback board beside it.", "RDAP gives a registration date of 10 April 2017 for financial-cents.com." ], "score": 76, "checks": [ { "check": "Legal entity named", "value": "Financial Cents LLC", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "financial-cents.com, registered 2017-04-10 (9 years)", "points": 11, "max": 15, "state": "part" }, { "check": "Endpoint on the vendor's domain", "value": "app.financial-cents.com", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "Privacy policy", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "Status page", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "not found", "points": 0, "max": 10, "state": "no" } ] }, "pageJsonUrl": "https://www.anchorterminal.com/tools/financial-cents-mcp.json", "live": { "slug": "financial-cents-mcp", "probe": { "target": "https://app.financial-cents.com/mcp", "method": "mcp-initialize", "lastAt": "2026-10-27T07:07:45.186515308Z", "lastOk": true, "lastStatus": 401, "lastMs": 232, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 181, "p95ms24h": 259, "samples24h": 25, "samples30d": 25, "days": [ { "date": "2026-10-27", "probes": 25, "ok": 25 } ] }, "updatedAt": "2026-10-27T07:07:45.186515308Z" } } }