Embat MCP server icon

Embat

by Embat

HIPAA CompliantSOC2 ReadyISO 27001 Ready
Finance1 tool

Query corporate treasury — cash, debt, payments, accounting and forecasts — from an AI agent. One tool, ask_tellme, that dispatches natural language to Embat's routing agent. OAuth sign-in, no application scopes, no payment initiation today.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Embat via MCP

https://tellme.embat.io/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Embat Tools & Capabilities (1)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • One tool name is not one operation. ask_tellme routes natural language to Embat's orchestrator, which dispatches to domain agents across every Embat module. The reachable operation count is unpublished, so no allowlist, verb census or scope grant can bound it.
  • No OAuth scope separates anything. The RFC 9728 descriptor declares scopes_supported: [] and the authorization server advertises only identity claims. There is no boundary between the routine read and any future write — the exact place a boundary would matter on a treasury connector.
  • Embat publishes no tool list. The single name comes from Anthropic's directory. Embat's entire 325-article help centre contains no mention of MCP, Claude or Anthropic, so no vendor enumeration exists to diff against.
  • The nominated documentation URL is about a different surface. It describes in-app TellMe, whose Silent Mode does perform unreviewed background writes. The connector runs Ask mode only. We had to find the connector's real documentation on Embat's marketing blog.
  • Embat's own article contradicts itself on "actions". It says Claude "can not act autonomously" and also that Ask mode covers "queries and actions you initiate". Embat's engineering blog resolves it — an action is a reviewable suggestion, not an execution — but a reader of the connector article alone gets two answers.
  • Read-only is dated, not structural. Embat has published its intent to add payment initiation and transaction approval through this connector during 2026. Nothing on the wire would change when it does: same endpoint, same tool name, same empty scope list.
  • We could not read tool schemas or annotations. The endpoint returned 401 to an anonymous request, so no parameter detail, readOnlyHint or destructiveHint is published here.
  • Answers are as fresh as the last bank sync, not live. Embat states sync is event-driven "typically every few minutes"; a balance reflects "the state of the accounts as of the last sync, not end-of-day or opening balance". Do not treat a returned figure as an intraday settlement position.
  • The connector inherits, and does not reduce, your Embat role. A user with payments Approve rights runs the agent session at that privilege level.
  • No metering signal either way. Neither Embat nor Anthropic publishes a per-call cost, quota or rate limit for this server, and no tool exists that could report usage or balance. We found nothing indicating a query spends money, but nothing confirming it does not.
  • The privacy policy omits the AI stack. Vertex AI's role is disclosed in a help-centre article; Embat's privacy policy names no AI sub-processor.

Frequently asked questions

Not today, on Embat's own statement. Embat writes that Claude cannot act autonomously through the connector and that it merely retrieves, synthesises and surfaces information. Embat also names payment initiation and transaction approval as roadmap items for 2026, which is an explicit statement that they are not shipped. Treat the read-only boundary as a current property, not a permanent one.

One tool name, an unknown number of operations. ask_tellme forwards natural language to Embat's Ask-mode agent, which Embat describes as an orchestrator routing to domain agents for categorisation, reconciliation and accounting, enrichment, treasury and forecasting. Each domain agent holds its own bounded action set that Embat never enumerates, so the tool count tells you nothing about reach.

Yes, and beneficiary details too. Embat's connector article shows queries returning per-entity and per-account balances, accounts below minimum thresholds, and pending payments listed with beneficiary, amount, currency and due date. Embat draws this from 15,000-plus financial institutions over PSD2, EBICS, host-to-host and SWIFT connections, synced every few minutes.

None that constrain anything. The server's RFC 9728 descriptor declares scopes_supported as an empty array, and its WorkOS AuthKit authorization server advertises only email, offline_access, openid and profile. Every one of those is an identity claim. No scope separates reading a balance from any other operation the server implements.

No, and that is the structural weakness of a one-tool natural-language server. An allowlist can permit or deny ask_tellme and nothing finer, because the operation is chosen by Embat's router from your sentence rather than by the tool name. Allowing the tool grants whatever its domain agents can reach, now and after Embat ships more.

Only as far as your own account already does. Embat states that the connector inherits your existing data-level permissions and enforces them on the server. Embat's payments module grades roles as View, Edit and Approve. A treasurer holding Approve carries that ladder into the agent session, so the boundary is your role, not the connector.

No, and this is easy to misread. The documentation URL Anthropic lists describes TellMe inside the Embat web app, including Silent Mode background writes to categorisations and forecasts. Those are product features, not connector tools. Embat's connector runs only Ask mode. The connector's real documentation is a post on embat.io, linked in Sources.

Existing Embat customers, authenticating with credentials they already hold. Embat states the integration authenticates through existing Embat credentials and that no new login or setup is required once the connector is added. Anthropic's directory records the server as a commercial, partner-tier remote connector requiring authentication, which our anonymous probe confirmed.

Sources

Use in Agentman

Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Server Info

Category
Finance
Developer
Embat
Tools
1
Domain
tellme.embat.io

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.