{ "data": { "a": { "slug": "merge-agent-handler", "name": "Merge Agent Handler", "vendor": "Merge API, Inc.", "vendorUrl": "https://www.merge.dev", "kind": "mcp", "category": "aggregator", "summary": "Merge Agent Handler is a hosted MCP server from Merge API, Inc. that gives AI agents tools across more than 190 third-party connectors, with per-user credentials, tool packs, a security gateway and logs of every call.", "url": "https://www.anchorterminal.com/tools/merge-agent-handler", "markdownUrl": "https://www.anchorterminal.com/tools/merge-agent-handler.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/merge-agent-handler.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/merge-agent-handler.json", "license": "Proprietary service under Merge's Master Services Agreement. The Merge CLI package `merge-api` on PyPI is marked MIT, and the repository its PyPI page links (github.com/merge-api/merge-cli) answered 404 on 8 October 2026", "transports": [ "streamable-http", "http" ], "remoteUrl": "https://ah-api.merge.dev/mcp", "packages": [ { "registry": "pypi", "name": "merge-api" } ], "auth": "mixed", "authNotes": "Self-serve. Each call carries an access key in `Authorization: Bearer \u003ckey\u003e` against `https://ah-api.merge.dev/api/v1/tool-packs/\u003cTOOL_PACK_ID\u003e/registered-users/\u003cREGISTERED_USER_ID\u003e/mcp`. The production key covers the whole organisation. `POST /api/v1/access-keys/` mints narrower keys that name Registered Users and Tool Packs, carry `runtime:all` or `management:all`, and expire. Test keys reach a separate sandbox. The simplified URL `https://ah-api.merge.dev/mcp` signs a person in with OAuth (it answered 401 with a `resource_metadata` pointer when we called it without credentials). End users connect each third-party account through Merge Link or a magic link, and Merge stores those credentials. The docs describe an unauthenticated `POST /api/v1/agent/signup/` that creates an organisation and returns a key. We did not call it.", "pricing": "freemium", "pricingNotes": "Free is 2,000 credits a month with no card, one credit per tool call, and tool calls answer 402 `billing_limit_reached` once the credits are spent. Pro is $1,000 a month for 25,000 credits, with steps listed at $1,175, $1,550, $2,250, $2,800 and $3,200 for 30,000, 40,000, 60,000, 80,000 and 100,000 credits, plus 2,000 bonus credits per the billing docs. Pro overage is billed at month end at a rate the pricing page doesn't state. Failed calls, blocked calls and test-key calls spend credits, and `tools/list` doesn't. Enterprise and Employees Pro are priced on contract (https://www.merge.dev/pricing/agent-handler, checked 2026-10-08).", "priceSummary": "$1000 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Agent Handler docs index, the OpenAPI file or the pricing page. The API's 402 is a plan limit, `billing_limit_reached`, not a payment protocol (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": 681, "asOf": "2026-10-08" }, "docsUrl": "https://docs.merge.dev/merge-agent-handler/overview", "llmsTxt": "https://docs.merge.dev/merge-agent-handler/llms.txt", "openapi": "https://docs.merge.dev/openapi/agent-handler-api.json", "capabilities": [ "automation.apps", "automation.auth", "automation.actions", "agent.tools", "auth.audit" ], "tags": [ "hosted", "mcp", "freemium", "free-tier", "no-card", "oauth", "openapi", "llms-txt", "cli", "python", "enterprise", "status-page", "soc2", "closed-source" ], "lastRelease": "2026-10-05", "graded": true, "anchor": { "graded": true, "score": 69.5, "grade": "B", "agentReady": false, "rank": 183, "ranked": true, "rankOf": 950, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 68, "maintenance": 69, "payments": 55, "reliability": 59, "schema": 80, "security": 83, "transparency": 71 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Agent Handler's access keys can be limited to named users, tool packs and a runtime scope, with an expiry, and an agent can create an account with one documented request. No rate limit figures are published, Pro starts at $1,000 a month with no published overage rate, and failed or blocked calls spend credits.", "bestFor": "A product team whose agent acts in customers' SaaS accounts and needs per-user credentials, key scoping, redaction rules and logs in one hosted layer, and teams already on Merge's Unified API.", "strengths": [ "Access keys can be limited to named Registered Users and Tool Packs and to the `runtime:all` scope, with an expiry. A child key is never wider than its parent", "The docs and OpenAPI file describe `POST /api/v1/agent/signup/`, which needs no credentials and returns a key, a tool pack and a registered user", "The Free plan has 2,000 credits a month, one per tool call, and the quickstart says signup needs no card", "Tool Call Logs record arguments, results, redactions and a latency breakdown per call, and every MCP result carries a request id that matches the log row", "Changelog entries for Agent Handler are dated 18 September, 25 September and 2 October 2026" ], "weaknesses": [ "No rate limit figures are published. The docs say only that MCP tool calls are limited per Registered User and per organisation, by the minute", "Pro starts at $1,000 a month for 25,000 credits, and the overage rate isn't on the pricing page", "Every `tools/call` spends a credit, including failed calls, calls blocked by a rule and calls made with a test key", "AI Guardrails let a call through when the evaluator fails or is unreachable, and new guardrails screen requests only, by default", "The master production key reaches every user and tool pack and can't be revoked, only regenerated. Agent signup returns an unrestricted key" ], "agentNotes": [ "Call `search_tools` with a plain-language intent before `tools/list`. A Tool Pack can hold hundreds of tools and Slack alone lists 50", "Add `?connectors=slack` to the MCP URL to limit a connection to named connectors, and `?paginated=true` only if the client follows `nextCursor`", "Carry a user-scoped key with `runtime:all` only. The production key reaches every Registered User and the management endpoints", "On `reauth_required` read `data.reauth_reason`, then call `authenticate_\u003cconnector\u003e` by name. Intent search doesn't return the authenticate tools", "Pin `MCP-Protocol-Version` to `2025-03-26` when context is tight. Later revisions repeat object results in `structuredContent`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 69.5 } ], "editorialScores": { "ergonomics": 68, "maintenance": 69, "payments": 55, "reliability": 59, "schema": 80, "security": 83, "transparency": 58 }, "provenanceScore": 83 }, "connect": { "install": "pipx install merge-api", "http": "curl -X POST \"https://ah-api.merge.dev/api/v1/tool-packs/$TOOL_PACK_ID/registered-users/$REGISTERED_USER_ID/mcp\" \\\n -H \"Authorization: Bearer $MERGE_AGENT_HANDLER_API_KEY\" -H \"Content-Type: application/json\" \\\n -H \"Accept: application/json, text/event-stream\" \\\n -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools/list\"}'", "claudeCode": "claude mcp add --transport http agent-handler https://ah-api.merge.dev/mcp", "config": { "mcpServers": { "agent-handler": { "headers": { "Authorization": "Bearer \u003cYOUR_API_KEY\u003e" }, "url": "https://ah-api.merge.dev/api/v1/tool-packs/\u003cTOOL_PACK_ID\u003e/registered-users/\u003cREGISTERED_USER_ID\u003e/mcp" } } } }, "letme": { "capability": "https://letme.dev/automation.apps", "tool": "https://letme.dev/merge-agent-handler" }, "sameCompany": [ "merge-accounting" ], "area": "business", "unitPrices": [ { "item": "Pro plan, 25,000 credits", "unit": "month", "usd": 1000, "note": "One credit per tool call. 2,000 bonus credits. Overage billed at month end, rate not published" }, { "item": "Pro plan, 100,000 credits", "unit": "month", "usd": 3200, "note": "Largest self-serve step on the pricing page" } ], "provenance": { "legalEntity": "Merge API, Inc.", "domain": "merge.dev", "domainRegistered": "2020-02-09", "endpointOnVendorDomain": true, "terms": "https://www.merge.dev/legal/msa", "privacy": "https://www.merge.dev/legal/privacy-policy", "statusPage": "https://status.merge.dev", "changelog": "https://www.merge.dev/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Master Services Agreement, last updated 9 September 2026, names Merge API, Inc., a Delaware corporation at 353 Sacramento St., Floor 21, San Francisco, CA 94111, and applies to a customer who clicks to accept or uses the Service. merge.dev/legal/terms is a Terms of Use for the website.", "A separate Subscriber Agreement (last updated 2 April 2026) is written around End Customers and Merge Integrations, the Unified API's terms. Neither agreement names Agent Handler, so the MSA is our reading of which one governs it.", "The privacy policy was last revised 20 August 2026. It leaves data processed for a customer to the customer agreement and the Data Processing Addendum.", "The API and MCP server answer at ah-api.merge.dev and the dashboard at ah.merge.dev.", "www.merge.dev/.well-known/security.txt returned 404. The security page gives security@merge.dev and a vulnerability disclosure programme.", "RDAP for merge.dev gives a registration date of 2020-02-09.", "status.merge.dev runs on Sorry and lists Merge Agent Handler as a component. It shows 30 days of notices." ], "score": 83 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/merge-agent-handler.json", "live": { "slug": "merge-agent-handler", "probe": { "target": "https://ah-api.merge.dev/mcp", "method": "mcp-initialize", "lastAt": "2026-10-10T03:53:34.162891121Z", "lastOk": true, "lastStatus": 401, "lastMs": 427, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 456, "p95ms24h": 1438, "samples24h": 209, "samples30d": 209, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 169 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://status.merge.dev", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:50:48.030989122Z" }, "versions": [ { "registry": "pypi", "name": "merge-api", "version": "0.5.0", "released": "2026-10-05", "seenAt": "2026-10-09T17:05:00.230768649Z" } ], "pypiWeekly": 708, "securityTxt": { "url": "https://merge.dev/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-09T15:39:39.570097881Z" }, "llmsTxt": { "url": "https://docs.merge.dev/merge-agent-handler/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:02:28.719651564Z" }, "pages": [ { "url": "https://www.merge.dev/pricing/agent-handler", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:52:17.837889276Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "540abebfdc1b" }, { "url": "https://www.merge.dev/legal/msa", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:52:09.678065655Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3561c8e50650" } ], "mcpTools": { "url": "https://ah-api.merge.dev/mcp", "checkedAt": "2026-10-09T21:40:45.658810474Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-09T21:40:45.658810474Z" }, "updatedAt": "2026-10-10T03:53:34.162891121Z" } }, "answer": "Merge Agent Handler scores 69.5 (B) on agent readiness against Unified.to MCP Server's 61.9 (C), and leads in 3 of 7 scored categories. Unified.to MCP Server leads on reliability and maintenance \u0026 community.", "b": { "slug": "unified-to-mcp", "name": "Unified.to MCP Server", "vendor": "Unified API Inc.", "vendorUrl": "https://unified.to", "kind": "mcp", "category": "aggregator", "summary": "Unified.to MCP Server is a hosted Streamable HTTP server from Unified API Inc. that turns one end-customer connection to a business app into MCP tools, on top of the vendor's unified API for CRM, HR, accounting and other categories.", "url": "https://www.anchorterminal.com/tools/unified-to-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/unified-to-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/unified-to-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/unified-to-mcp.json", "repo": "https://github.com/unified-to/unified-mcp-typescript", "license": "Proprietary service under Unified.to's Terms of Service. The linked repository is sample client code", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp-api.unified.to/mcp", "packages": [ { "registry": "npm", "name": "@unified-api/typescript-sdk" } ], "auth": "mixed", "authNotes": "Self-serve. A person signs in to app.unified.to with Google or GitHub and copies a workspace API key. Sent as `Authorization: Bearer \u003ckey\u003e` with `connection=\u003cid\u003e` in the URL, it lists that connection's tools, and without a connection it lists workspace management tools. The docs warn that the key reaches every connection and the whole account. The management tool `get_unified_connection_mcp_url` in `user` mode returns a URL with a signed token limited to one connection. Enterprise-managed authorisation exchanges an identity provider's assertion at `POST /oauth/token` for an `ema_` token that lasts 3,600 seconds and carries category read and write scopes. Unified turns it on per workspace on request. `?token=` still works for keys and is marked deprecated.", "pricing": "paid", "pricingNotes": "Plans from $750 a month. Grow is $750+ with 750,000 API calls and $1.00 per 1,000 beyond that, Pro $1,500+ with 2,000,000 and $0.75, Scale $3,000+ with 6,000,000 and $0.50, and Enterprise is priced on contract. Each MCP tool call counts as one API request, and the FAQ says successful calls are billable. A tester account starts with 2,500 free API requests and Grow and Pro start with a 30-day free trial. The page does not say whether a card is needed (https://unified.to/pricing, checked 2026-10-09).", "priceSummary": "$750 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the MCP docs pages, the pricing page or the Terms of Service (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 22019, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.unified.to/mcp/overview", "llmsTxt": "https://docs.unified.to/llms.txt", "openapi": "https://api.unified.to/openapi.json", "registryName": "to.unified/core", "capabilities": [ "automation.apps", "automation.auth", "automation.actions", "agent.tools", "automation.webhooks" ], "tags": [ "hosted", "mcp", "paid", "free-trial", "api-key", "openapi", "llms-txt", "typescript", "python", "status-page", "soc2", "mcp-registry", "closed-source", "data-residency" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 61.9, "grade": "C", "agentReady": false, "rank": 455, "ranked": true, "rankOf": 950, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 71, "maintenance": 84, "payments": 30, "reliability": 73, "schema": 81, "security": 50, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -3, "negativeNotes": [ "23 September 2026. The MCP changelog entry of that date removed the SSE transport (`/sse` and `/sse/messages` now return HTTP 410), dropped `sse_url` from the `get_unified_connection_mcp_url` response, which the docs label a breaking change, and stopped regions resolving across one another. No earlier notice was found in the MCP changelog, the site changelog or the September product update. Whether customers were told privately was not established. The migration is a one-word URL change and is documented, so 3 points (https://docs.unified.to/mcp/changelog)." ], "verdict": "Every previewed tool carries a typed input schema and read-only, destructive and idempotent annotations, and the list can be narrowed by permission or tool name. The default credential is a workspace API key that reaches every connection, and the SSE transport was removed on 23 September 2026 in the changelog entry that announced it.", "bestFor": "A B2B software team that already uses or plans to use Unified's API and wants the same customer connections exposed to an LLM, with data read live from the source app.", "strengths": [ "A credential-free preview of the HubSpot tool list returned 78 tools, each with a JSON Schema input and `readOnlyHint`, `destructiveHint` and `idempotentHint` annotations, and 66 with an output schema", "The `permissions` and `tools` URL parameters limit which tools a connection lists, and `hide_sensitive` strips names, emails and telephone numbers from results", "A `user` mode URL carries a signed token limited to one connection, so the workspace API key need not be shared with an end customer", "Rate limits are published per plan, from 500 requests a minute on Test to 10,000 on Scale, shared across the workspace", "The privacy policy has an MCP section. It says end-customer data is not stored or cached and that Unified does not train models on any data", "The MCP changelog is dated and had entries on 22 July, 21 and 23 September and 8 October 2026" ], "weaknesses": [ "The default credential is a workspace API key. The docs say it grants access to all connections and the whole Unified.to account", "The `/sse` transport and the `sse_url` response field were removed on 23 September 2026. No earlier notice was found in the MCP changelog, the site changelog or the September update", "The connection-scoped signed token travels in the URL as `?token=`. The docs mark `?token=` authentication as deprecated, with no end date set", "One HubSpot connection lists 78 tools whose definitions come to about 133 KB without output schemas and 343 KB with them", "No uptime SLA is published. The pricing page says SLAs come with a custom Enterprise plan", "No security.txt, bug bounty or disclosure policy was found, and the security page gives February 2025 as its last review", "The Terms of Service forbid probing, scanning or testing the vulnerability of the service. This matters before any probe is run", "The Terms of Service bar transmitting financial or medical information and birth dates through the service, while the product sells accounting and HR integrations" ], "agentNotes": [ "Use the host for the workspace's region. US is `mcp-api.unified.to`, EU is `mcp-api-eu.unified.to` and AU is `api-au.unified.to`. A credential on another region's host resolves to not found", "Send the key as `Authorization: Bearer \u003ckey\u003e` and put `connection=\u003cid\u003e` in the URL. Without `connection` the server lists workspace management tools, not the customer's data tools", "Pass `tools` or `permissions` in the URL before listing. An unfiltered connection can list dozens of tools with large output schemas", "Expect HTTP 429 on tool calls since 23 September 2026. Unified does not queue or retry, so back off and retry yourself", "Page with `limit` (100 at most on most endpoints) and `offset`, and stop when a page returns fewer records than `limit`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.9 } ], "editorialScores": { "ergonomics": 71, "maintenance": 84, "payments": 30, "reliability": 73, "schema": 81, "security": 50, "transparency": 61 }, "provenanceScore": 71 }, "connect": { "claudeCode": "claude mcp add --transport http unified-core https://mcp-api.unified.to/mcp \\\n --header \"Authorization: Bearer $UNIFIED_API_KEY\"", "config": { "mcpServers": { "unified-mcp": { "headers": { "Authorization": "Bearer XXXXXXXX" }, "url": "https://mcp-api.unified.to/mcp?connection=YYYYYYY" } } } }, "letme": { "capability": "https://letme.dev/automation.apps", "tool": "https://letme.dev/unified-to-mcp" }, "area": "business", "unitPrices": [ { "item": "Grow plan", "unit": "month", "usd": 750, "note": "Listed as $750+ a month. 750,000 API calls a month, each tool call counting as one" }, { "item": "Pro plan", "unit": "month", "usd": 1500, "note": "Listed as $1,500+ a month. 2,000,000 API calls a month" }, { "item": "Scale plan", "unit": "month", "usd": 3000, "note": "Listed as $3,000+ a month. 6,000,000 API calls a month" }, { "item": "Overage, Grow", "unit": "1k-requests", "usd": 1, "note": "Per 1,000 API calls beyond the plan allowance" }, { "item": "Overage, Pro", "unit": "1k-requests", "usd": 0.75, "note": "Per 1,000 API calls beyond the plan allowance" }, { "item": "Overage, Scale", "unit": "1k-requests", "usd": 0.5, "note": "Per 1,000 API calls beyond the plan allowance" } ], "provenance": { "legalEntity": "Unified API Inc.", "domain": "unified.to", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://unified.to/tos", "privacy": "https://unified.to/privacy", "statusPage": "https://status.unified.to", "changelog": "https://docs.unified.to/mcp/changelog", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Terms of Service say the site and the service are operated by Unified API Inc. and are governed by the laws of the Province of Ontario. The page carries no date.", "The DPA, last revised 19 March 2026, names UNIFIED API Inc., an Ontario corporation at 325 Front Street West, 4th floor, Toronto.", "The privacy policy covers unified.to, api.unified.to, app.unified.to and sub-domains, and has a section on the MCP server at mcp-api.unified.to.", "The MCP endpoints answer at mcp-api.unified.to, mcp-api-eu.unified.to and api-au.unified.to.", "unified.to/.well-known/security.txt returned 404.", "status.unified.to runs on Honeybadger and lists the API and the admin app in three regions and the authentication page. The MCP server has no component of its own. The docs say it runs as part of the API.", "The registration date of unified.to was not looked up. The .to registry publishes no RDAP record we know of.", "The trust centre at app.mycroft.io/trust/unified-to was not read." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/unified-to-mcp.json", "live": { "slug": "unified-to-mcp", "probe": { "target": "https://mcp-api.unified.to/mcp", "method": "mcp-initialize", "lastAt": "2026-10-10T03:53:47.961821287Z", "lastOk": true, "lastStatus": 401, "lastMs": 261, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 272, "p95ms24h": 773, "samples24h": 125, "samples30d": 125, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://status.unified.to", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:51:21.9050769Z" }, "versions": [ { "registry": "mcp-registry", "name": "to.unified/core", "version": "1.0.0", "seenAt": "2026-10-10T03:11:32.438759038Z" }, { "registry": "npm", "name": "@unified-api/typescript-sdk", "version": "2.85.49", "seenAt": "2026-10-09T17:25:58.700208637Z" } ], "githubStars": 1, "npmWeekly": 22019, "pages": [ { "url": "https://docs.unified.to/mcp/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:38:38.189021839Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "1e120959fd1f" }, { "url": "https://unified.to/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:46:56.977008444Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9dfee61b4129" }, { "url": "https://unified.to/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:46:59.381440787Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d1a0df8d57c0" }, { "url": "https://unified.to/tos", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:47:01.426629726Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f8ca80a1186d" } ], "mcpTools": { "url": "https://mcp-api.unified.to/mcp", "checkedAt": "2026-10-09T21:40:56.064886705Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-09T21:40:56.064886705Z" }, "updatedAt": "2026-10-10T03:53:47.961821287Z" } }, "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Merge API, Inc.", "b": "Unified API Inc.", "name": "Vendor" }, { "a": "https://ah-api.merge.dev/mcp", "b": "https://mcp-api.unified.to/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP, HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Merge's Master Services Agreement. The Merge CLI package `merge-api` on PyPI is marked MIT, and the repository its PyPI page links (github.com/merge-api/merge-cli) answered 404 on 8 October 2026", "b": "Proprietary service under Unified.to's Terms of Service. The linked repository is sample client code", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "to.unified/core", "name": "MCP registry" }, { "a": "2026-10-05", "b": "2026-10-08", "name": "Last release" }, { "a": "2026-09-09", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-08-20", "b": "2026-10-02", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "681 PyPI/wk", "b": "22k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Merge Agent Handler scores 69.5 (B) on agent readiness against Unified.to MCP Server's 61.9 (C), and leads in 3 of 7 scored categories. Unified.to MCP Server leads on reliability and maintenance \u0026 community.", "question": "Which is better for AI agents, Merge Agent Handler or Unified.to MCP Server?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Merge Agent Handler and Unified.to MCP Server need an API key?" }, { "answer": "Yes. Merge Agent Handler has a hosted endpoint at https://ah-api.merge.dev/mcp and Unified.to MCP Server at https://mcp-api.unified.to/mcp.", "question": "Can an agent call Merge Agent Handler and Unified.to MCP Server without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 83 against 50", "Payments \u0026 pricing, 55 against 30", "Transparency \u0026 trust, 71 against 66" ], "also": [ "Free to start without a card", "No incidents deducted, where Unified.to MCP Server loses 3 points for them" ], "goodFor": "A product team whose agent acts in customers' SaaS accounts and needs per-user credentials, key scoping, redaction rules and logs in one hosted layer, and teams already on Merge's Unified API.", "slug": "merge-agent-handler", "watchFor": "No rate limit figures are published. The docs say only that MCP tool calls are limited per Registered User and per organisation, by the minute" }, { "aheadOn": [ "Reliability, 73 against 59", "Maintenance \u0026 community, 84 against 69" ], "also": null, "goodFor": "A B2B software team that already uses or plans to use Unified's API and wants the same customer connections exposed to an LLM, with data read live from the source app.", "slug": "unified-to-mcp", "watchFor": "The default credential is a workspace API key. The docs say it grants access to all connections and the whole Unified.to account" } ], "job": { "capability": "automation.apps", "name": "App automation" }, "others": [ { "json": "https://www.anchorterminal.com/compare/composio-rube-vs-merge-agent-handler.json", "title": "Composio (API + MCP) vs Merge Agent Handler", "url": "https://www.anchorterminal.com/compare/composio-rube-vs-merge-agent-handler" }, { "json": "https://www.anchorterminal.com/compare/composio-rube-vs-unified-to-mcp.json", "title": "Composio (API + MCP) vs Unified.to MCP Server", "url": "https://www.anchorterminal.com/compare/composio-rube-vs-unified-to-mcp" }, { "json": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-one.json", "title": "Merge Agent Handler vs One", "url": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-one" }, { "json": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-smithery.json", "title": "Merge Agent Handler vs Smithery", "url": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-smithery" }, { "json": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-stackone.json", "title": "Merge Agent Handler vs StackOne", "url": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-stackone" }, { "json": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-zapier-mcp.json", "title": "Merge Agent Handler vs Zapier MCP (agent actions)", "url": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-zapier-mcp" }, { "json": "https://www.anchorterminal.com/compare/one-vs-unified-to-mcp.json", "title": "One vs Unified.to MCP Server", "url": "https://www.anchorterminal.com/compare/one-vs-unified-to-mcp" }, { "json": "https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp.json", "title": "Smithery vs Unified.to MCP Server", "url": "https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp" }, { "json": "https://www.anchorterminal.com/compare/stackone-vs-unified-to-mcp.json", "title": "StackOne vs Unified.to MCP Server", "url": "https://www.anchorterminal.com/compare/stackone-vs-unified-to-mcp" }, { "json": "https://www.anchorterminal.com/compare/unified-to-mcp-vs-zapier-mcp.json", "title": "Unified.to MCP Server vs Zapier MCP (agent actions)", "url": "https://www.anchorterminal.com/compare/unified-to-mcp-vs-zapier-mcp" }, { "json": "https://www.anchorterminal.com/compare/letme-vs-merge-agent-handler.json", "title": "letme vs Merge Agent Handler", "url": "https://www.anchorterminal.com/compare/letme-vs-merge-agent-handler" }, { "json": "https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp.json", "title": "letme vs Unified.to MCP Server", "url": "https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp" } ], "scores": [ { "by": 14, "edge": "unified-to-mcp", "key": "reliability", "merge-agent-handler": 59, "name": "Reliability", "unified-to-mcp": 73, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 1, "edge": "unified-to-mcp", "key": "schema", "merge-agent-handler": 80, "name": "Schema \u0026 documentation", "unified-to-mcp": 81, "weight": 13 }, { "by": 3, "edge": "unified-to-mcp", "key": "ergonomics", "merge-agent-handler": 68, "name": "Agent ergonomics", "unified-to-mcp": 71, "weight": 13 }, { "by": 33, "edge": "merge-agent-handler", "key": "security", "merge-agent-handler": 83, "name": "Security \u0026 auth", "unified-to-mcp": 50, "weight": 14 }, { "by": 25, "edge": "merge-agent-handler", "key": "payments", "merge-agent-handler": 55, "name": "Payments \u0026 pricing", "unified-to-mcp": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 15, "edge": "unified-to-mcp", "key": "maintenance", "merge-agent-handler": 69, "name": "Maintenance \u0026 community", "unified-to-mcp": 84, "weight": 7 }, { "by": 5, "edge": "merge-agent-handler", "key": "transparency", "merge-agent-handler": 71, "name": "Transparency \u0026 trust", "unified-to-mcp": 66, "weight": 7 } ], "summary": "Merge Agent Handler scores 69.5 (B) on agent readiness against Unified.to MCP Server's 61.9 (C), and leads in 3 of 7 scored categories. Unified.to MCP Server leads on reliability and maintenance \u0026 community. Both do app automation.", "verdicts": { "merge-agent-handler": "Agent Handler's access keys can be limited to named users, tool packs and a runtime scope, with an expiry, and an agent can create an account with one documented request. No rate limit figures are published, Pro starts at $1,000 a month with no published overage rate, and failed or blocked calls spend credits.", "unified-to-mcp": "Every previewed tool carries a typed input schema and read-only, destructive and idempotent annotations, and the list can be narrowed by permission or tool name. The default credential is a workspace API key that reaches every connection, and the SSE transport was removed on 23 September 2026 in the changelog entry that announced it." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-unified-to-mcp", "json": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-unified-to-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-unified-to-mcp.md", "slim": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-unified-to-mcp.min.md" }, "markdown": "Merge Agent Handler scores 69.5 (B) on agent readiness against Unified.to MCP Server's 61.9 (C), and leads in 3 of 7 scored categories. Unified.to MCP Server leads on reliability and maintenance \u0026 community. Both do app automation.\n\n- Merge Agent Handler: grade B, 69.5/100, rank #183 of 950. Markdown https://www.anchorterminal.com/tools/merge-agent-handler.md · JSON https://www.anchorterminal.com/api/v1/tools/merge-agent-handler.json\n- Unified.to MCP Server: grade C, 61.9/100, rank #455 of 950. Markdown https://www.anchorterminal.com/tools/unified-to-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/unified-to-mcp.json\n- Best agent tool access platforms: https://www.anchorterminal.com/best/aggregator/index.md\n- All 28 tool access comparisons: https://www.anchorterminal.com/compare/aggregator/index.md\n\n## Which one, for what\n\n### Merge Agent Handler (B)\n\nGood for: A product team whose agent acts in customers' SaaS accounts and needs per-user credentials, key scoping, redaction rules and logs in one hosted layer, and teams already on Merge's Unified API.\n\nAhead on:\n- Security \u0026 auth, 83 against 50\n- Payments \u0026 pricing, 55 against 30\n- Transparency \u0026 trust, 71 against 66\n\nAlso in its favour:\n- Free to start without a card\n- No incidents deducted, where Unified.to MCP Server loses 3 points for them\n\nWatch for: No rate limit figures are published. The docs say only that MCP tool calls are limited per Registered User and per organisation, by the minute\n\n### Unified.to MCP Server (C)\n\nGood for: A B2B software team that already uses or plans to use Unified's API and wants the same customer connections exposed to an LLM, with data read live from the source app.\n\nAhead on:\n- Reliability, 73 against 59\n- Maintenance \u0026 community, 84 against 69\n\nWatch for: The default credential is a workspace API key. The docs say it grants access to all connections and the whole Unified.to account\n\n\n## Score by category\n\n| Category | Weight | Merge Agent Handler | Unified.to MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 59 | 73 | Unified.to MCP Server +14 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 80 | 81 | Unified.to MCP Server +1 |\n| Agent ergonomics | 13% (16.2 this run) | 68 | 71 | Unified.to MCP Server +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 83 | 50 | Merge Agent Handler +33 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 55 | 30 | Merge Agent Handler +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 69 | 84 | Unified.to MCP Server +15 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 71 | 66 | Merge Agent Handler +5 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **69.5 · B** | **61.9 · C** | |\n\n## Facts side by side\n\n| Fact | Merge Agent Handler | Unified.to MCP Server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Merge API, Inc. | Unified API Inc. |\n| Hosted endpoint | `https://ah-api.merge.dev/mcp` | `https://mcp-api.unified.to/mcp` |\n| Transports | Streamable HTTP, HTTP | Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Merge's Master Services Agreement. The Merge CLI package `merge-api` on PyPI is marked MIT, and the repository its PyPI page links (github.com/merge-api/merge-cli) answered 404 on 8 October 2026 | Proprietary service under Unified.to's Terms of Service. The linked repository is sample client code |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `to.unified/core` |\n| Last release | 2026-10-05 | 2026-10-08 |\n| Terms last updated | 2026-09-09 | no date given |\n| Privacy policy last updated | 2026-08-20 | 2026-10-02 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 681 PyPI/wk | 22k npm/wk |\n\n## Verdicts\n\n**Merge Agent Handler.** Agent Handler's access keys can be limited to named users, tool packs and a runtime scope, with an expiry, and an agent can create an account with one documented request. No rate limit figures are published, Pro starts at $1,000 a month with no published overage rate, and failed or blocked calls spend credits.\n\n**Unified.to MCP Server.** Every previewed tool carries a typed input schema and read-only, destructive and idempotent annotations, and the list can be narrowed by permission or tool name. The default credential is a workspace API key that reaches every connection, and the SSE transport was removed on 23 September 2026 in the changelog entry that announced it.\n\n## Before you call either\n\n### Merge Agent Handler\n\n1. Call `search_tools` with a plain-language intent before `tools/list`. A Tool Pack can hold hundreds of tools and Slack alone lists 50\n2. Add `?connectors=slack` to the MCP URL to limit a connection to named connectors, and `?paginated=true` only if the client follows `nextCursor`\n3. Carry a user-scoped key with `runtime:all` only. The production key reaches every Registered User and the management endpoints\n4. On `reauth_required` read `data.reauth_reason`, then call `authenticate_\u003cconnector\u003e` by name. Intent search doesn't return the authenticate tools\n5. Pin `MCP-Protocol-Version` to `2025-03-26` when context is tight. Later revisions repeat object results in `structuredContent`\n\n### Unified.to MCP Server\n\n1. Use the host for the workspace's region. US is `mcp-api.unified.to`, EU is `mcp-api-eu.unified.to` and AU is `api-au.unified.to`. A credential on another region's host resolves to not found\n2. Send the key as `Authorization: Bearer \u003ckey\u003e` and put `connection=\u003cid\u003e` in the URL. Without `connection` the server lists workspace management tools, not the customer's data tools\n3. Pass `tools` or `permissions` in the URL before listing. An unfiltered connection can list dozens of tools with large output schemas\n4. Expect HTTP 429 on tool calls since 23 September 2026. Unified does not queue or retry, so back off and retry yourself\n5. Page with `limit` (100 at most on most endpoints) and `offset`, and stop when a page returns fewer records than `limit`\n\n## Questions\n\n### Which is better for AI agents, Merge Agent Handler or Unified.to MCP Server?\n\nMerge Agent Handler scores 69.5 (B) on agent readiness against Unified.to MCP Server's 61.9 (C), and leads in 3 of 7 scored categories. Unified.to MCP Server leads on reliability and maintenance \u0026 community.\n\n### Do Merge Agent Handler and Unified.to MCP Server need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Merge Agent Handler and Unified.to MCP Server without installing anything?\n\nYes. Merge Agent Handler has a hosted endpoint at https://ah-api.merge.dev/mcp and Unified.to MCP Server at https://mcp-api.unified.to/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/merge-agent-handler-vs-unified-to-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/merge-agent-handler-vs-unified-to-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"merge-agent-handler\", \"b\": \"unified-to-mcp\"}`. From a terminal: `anchor compare merge-agent-handler unified-to-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/merge-agent-handler.json and https://www.anchorterminal.com/api/v1/tools/unified-to-mcp.json\n\n## Other comparisons with Merge Agent Handler or Unified.to MCP Server\n\n- [Composio (API + MCP) vs Merge Agent Handler](https://www.anchorterminal.com/compare/composio-rube-vs-merge-agent-handler.md)\n- [Composio (API + MCP) vs Unified.to MCP Server](https://www.anchorterminal.com/compare/composio-rube-vs-unified-to-mcp.md)\n- [Merge Agent Handler vs One](https://www.anchorterminal.com/compare/merge-agent-handler-vs-one.md)\n- [Merge Agent Handler vs Smithery](https://www.anchorterminal.com/compare/merge-agent-handler-vs-smithery.md)\n- [Merge Agent Handler vs StackOne](https://www.anchorterminal.com/compare/merge-agent-handler-vs-stackone.md)\n- [Merge Agent Handler vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/merge-agent-handler-vs-zapier-mcp.md)\n- [One vs Unified.to MCP Server](https://www.anchorterminal.com/compare/one-vs-unified-to-mcp.md)\n- [Smithery vs Unified.to MCP Server](https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp.md)\n- [StackOne vs Unified.to MCP Server](https://www.anchorterminal.com/compare/stackone-vs-unified-to-mcp.md)\n- [Unified.to MCP Server vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/unified-to-mcp-vs-zapier-mcp.md)\n- [letme vs Merge Agent Handler](https://www.anchorterminal.com/compare/letme-vs-merge-agent-handler.md)\n- [letme vs Unified.to MCP Server](https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Merge Agent Handler vs Unified.to MCP Server", "url": "" } ], "description": "Merge Agent Handler scores 69.5 (B) to Unified.to's 61.9 (C) for app automation. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Merge Agent Handler B 69.5", "Unified.to MCP Server C 61.9", "scores" ], "h1": "Merge Agent Handler vs Unified.to MCP Server", "image": "https://www.anchorterminal.com/assets/og/compare-merge-agent-handler-vs-unified-to-mcp.png", "path": "/compare/merge-agent-handler-vs-unified-to-mcp", "published": "2026-10-01", "section": "tools", "title": "Merge Agent Handler vs Unified.to for AI agents (2026)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-unified-to-mcp" }, "tokens": { "markdown": 2500, "slim": 730 }, "version": 1 }