{
  "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-10T02:07:15.931868803Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 1420,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 459,
          "p95ms24h": 1439,
          "samples24h": 191,
          "samples30d": 191,
          "days": [
            {
              "date": "2026-10-09",
              "probes": 169,
              "ok": 169
            },
            {
              "date": "2026-10-10",
              "probes": 22,
              "ok": 22
            }
          ]
        },
        "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-10T02:07:15.931868803Z"
      }
    },
    "answer": "Merge Agent Handler and StackOne score within a point of each other on agent readiness, 69.5 (B) and 69.1 (B). StackOne leads on reliability, agent ergonomics and maintenance \u0026 community.",
    "b": {
      "slug": "stackone",
      "name": "StackOne",
      "vendor": "StackOne Technologies Limited",
      "vendorUrl": "https://www.stackone.com",
      "kind": "mcp",
      "category": "aggregator",
      "summary": "StackOne is a hosted gateway from StackOne Technologies Limited that gives AI agents actions across more than 540 business apps over MCP, SDKs, A2A or HTTP, with managed authentication, per-user grants, policies and logs.",
      "url": "https://www.anchorterminal.com/tools/stackone",
      "markdownUrl": "https://www.anchorterminal.com/tools/stackone.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/stackone.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/stackone.json",
      "repo": "https://github.com/StackOneHQ/stackone-ai-node",
      "license": "Proprietary service under StackOne's SaaS Terms and Conditions. The Agent SDKs (`@stackone/ai`, `stackone-ai`) and the Defender package (`@stackone/defender`) are Apache-2.0",
      "transports": [
        "streamable-http",
        "http"
      ],
      "remoteUrl": "https://mcp.stackone.com/mcp",
      "packages": [
        {
          "registry": "npm",
          "name": "@stackone/ai"
        },
        {
          "registry": "pypi",
          "name": "stackone-ai"
        },
        {
          "registry": "npm",
          "name": "@stackone/defender"
        }
      ],
      "auth": "mixed",
      "authNotes": "Self-serve. A person signs up in the dashboard, creates a project and a connector profile, and links an account. MCP clients connect to `https://mcp.stackone.com/mcp` with OAuth (scopes `mcp offline_access`, one-hour access tokens, a 90-day grant) and the user picks the linked accounts and actions at consent. Most clients register themselves, and a few need a client ID and secret created in the dashboard. Backend calls go to `https://api.stackone.com/mcp` or `POST /actions/rpc` with a project API key as the Basic auth username and the linked account in `x-account-id`. Keys take scopes (Platform API, Actions, Connectors, Credentials, Unified API) and can be disabled or deleted. Session token URLs (`https://api.stackone.com/mcp?token=...`) cover one linked account, carry the access in the URL and expire after one year by default.",
      "pricing": "freemium",
      "pricingNotes": "Free to start with no card, per the pricing page. Gateway Starter is free with 1,000 credits a seat a month, one credit per tool call or API call, and extra credits at $60 per 20,000. Gateway Team is $600 a month ($6,000 a year) with 5,000 credits a seat a month and extra credits at $20 per 20,000. The pricing calculator's markup gives 10 seats included on Team and $15 a further seat, which the page text doesn't state. OEM Core is free with a monthly credit allowance and volume prices on request. Enterprise plans are priced on contract. Browser use, premium defence and data sync cost more than one credit, at rates not published. The Service Consumption Schedule of 30 March 2026 gives $0.003 per Action Call as overage and counts unsuccessful requests, while the pricing page says background and failed calls aren't billed (https://www.stackone.com/pricing/, checked 2026-10-09).",
      "priceSummary": "$600 / mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the docs index, the pricing page, the SaaS terms or the Service Consumption Schedule (checked 2026-10-09).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 30,
        "npmWeekly": 277,
        "pypiWeekly": null,
        "asOf": "2026-10-09"
      },
      "docsUrl": "https://docs.stackone.com/introduction",
      "llmsTxt": "https://docs.stackone.com/llms.txt",
      "openapi": "https://api.eu1.stackone.com/v2/oas/stackone.json",
      "registryName": "com.stackone/mcp",
      "capabilities": [
        "automation.apps",
        "automation.auth",
        "automation.actions",
        "agent.tools",
        "auth.audit"
      ],
      "tags": [
        "hosted",
        "mcp",
        "a2a",
        "freemium",
        "free-tier",
        "no-card",
        "oauth",
        "api-key",
        "openapi",
        "llms-txt",
        "typescript",
        "python",
        "enterprise",
        "status-page",
        "soc2",
        "mcp-registry",
        "closed-source"
      ],
      "lastRelease": "2026-09-24",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 69.1,
        "grade": "B",
        "agentReady": false,
        "rank": 198,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 3,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 75,
          "maintenance": 84,
          "payments": 38,
          "reliability": 80,
          "schema": 78,
          "security": 69,
          "transparency": 69
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-09"
        },
        "negative": -2,
        "negativeNotes": [
          "27 April 2026. `@stackone/ai` v2.8.1 fixed a flaw in which tools fetched concurrently for several accounts were stamped with the wrong `x-account-id`, so a call could run against another linked account. It is recorded as a bug fix in the changelog, with no advisory found. Fixed and documented, so 2 points (https://github.com/StackOneHQ/stackone-ai-node/blob/main/CHANGELOG.md)."
        ],
        "verdict": "StackOne's MCP server signs each person in with OAuth, lets them grant individual accounts and actions, and by default exposes two search and execute tools in place of the full catalogue. Session token URLs carry the credential in the query string for a year by default, and the Consumption Schedule and pricing page disagree on whether failed calls are billed.",
        "bestFor": "A company that wants one governed MCP endpoint for staff agents across business systems, and product teams embedding per-customer connections with HR, recruiting and CRM coverage.",
        "strengths": [
          "The MCP server at `https://mcp.stackone.com/mcp` uses OAuth per person. Access tokens last one hour, a grant lasts 90 days, and each user can revoke it under Connected Apps",
          "Advanced Tool Search replaces the tool list with two tools, search and execute, and is on by default at the OAuth consent screen",
          "Since 24 July 2026 every tool carries `readOnlyHint`, `destructiveHint` and `openWorldHint`, derived from an effects value on each action",
          "API keys are limited to one project and take scopes for the Platform API, Actions, Connectors, Credentials and the Unified API. Credentials access is off by default",
          "Rate limit published at 1,000 requests a minute per API key, with `Retry-After` in seconds on 429 and 408 responses",
          "Defender scans tool results for prompt injection and is on for new projects. Its Light Scan engine is open source under Apache-2.0"
        ],
        "weaknesses": [
          "Session token URLs (`https://api.stackone.com/mcp?token=...`) put the credential in the query string, cover one linked account and expire after one year by default",
          "The Service Consumption Schedule counts every request, successful or not, as an Action Call. The pricing page says failed calls aren't billed",
          "Defender's default mode is Monitor, which records a verdict and passes the tool result to the agent unchanged",
          "Policies apply only to signed-in members. A call made with a project API key is memberless and is governed by connector profile scoping alone",
          "The Logs API, audit logs, SIEM export and an uptime SLA are Enterprise only on Gateway plans, and Starter keeps action logs for one day",
          "The Acceptable Use Policy bars competitive analysis or benchmarking other than for internal comparison, and probing or testing the Service's vulnerability without authorisation. This matters before any probe is run",
          "`@stackone/ai` stamped tools with the wrong `x-account-id` when accounts were fetched concurrently, until v2.8.1 on 27 April 2026. No advisory was found"
        ],
        "agentNotes": [
          "Send `Accept: application/json,text/event-stream` on every MCP request to `https://api.stackone.com/mcp`, by POST only. Without it the server answers 406",
          "In `search_execute` mode call `{provider}_search_actions` first and pass the returned `action_id` to `{provider}_execute_action`. Never hardcode action ids",
          "Pass the API key as the Basic auth username with an empty password, and name the linked account in `x-account-id`",
          "On 429 or 408 wait the seconds given in `Retry-After`. StackOne has already retried a provider's 429 up to five times within a 60-second request lifetime",
          "On 412 read `errorCode` and `details.statusReasons`. `AccountErrorStatus` needs a person to re-authenticate the linked account"
        ],
        "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.1
          }
        ],
        "editorialScores": {
          "ergonomics": 75,
          "maintenance": 84,
          "payments": 38,
          "reliability": 80,
          "schema": 78,
          "security": 69,
          "transparency": 50
        },
        "provenanceScore": 88
      },
      "connect": {
        "install": "npm install @stackone/ai",
        "http": "curl -X POST \"https://api.stackone.com/actions/rpc\" \\\n  -u \"$STACKONE_API_KEY:\" \\\n  -H \"x-account-id: your-account-id\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\"action\": \"bamboohr_list_employees\", \"query\": {\"page_size\": 25}}'",
        "claudeCode": "claude mcp add --transport http --scope user stackone https://mcp.stackone.com/mcp"
      },
      "letme": {
        "capability": "https://letme.dev/automation.apps",
        "tool": "https://letme.dev/stackone"
      },
      "area": "business",
      "unitPrices": [
        {
          "item": "Gateway Team plan",
          "unit": "month",
          "usd": 600,
          "note": "5,000 credits a seat a month, one credit per tool call or API call. $6,000 billed yearly"
        },
        {
          "item": "Extra credits, Gateway Starter",
          "unit": "1k-calls",
          "usd": 3,
          "note": "$60 per 20,000 credits, valid 12 months. Advanced capabilities cost more than one credit a call"
        },
        {
          "item": "Extra credits, Gateway Team",
          "unit": "1k-calls",
          "usd": 1,
          "note": "$20 per 20,000 credits, valid 12 months"
        }
      ],
      "provenance": {
        "legalEntity": "StackOne Technologies Limited",
        "domain": "stackone.com",
        "domainRegistered": "2013-06-25",
        "endpointOnVendorDomain": true,
        "terms": "https://www.stackone.com/terms/saas-terms/",
        "privacy": "https://www.stackone.com/terms/privacy-policy/",
        "statusPage": "https://status.stackone.com",
        "changelog": "https://www.stackone.com/changelog/",
        "securityTxt": "none",
        "checked": "2026-10-09",
        "notes": [
          "The SaaS Terms and Conditions, effective 30 March 2026, name StackOne Technologies Limited, company number 14684360, registered at 2 Communications Road, Newbury, Berkshire, RG19 6AB, under the laws of England and Wales. They take effect when a customer first accesses the Service or signs an order.",
          "The contact page says StackOne operates in the United States as StackOne Technologies Inc., 2261 Market Street, San Francisco.",
          "The Platform Privacy Policy, last updated 1 December 2023, covers the web application and API and says it does not cover the website. A separate Privacy Notice covers the website.",
          "The MCP server answers at mcp.stackone.com, the API at api.stackone.com and A2A at a2a.stackone.com.",
          "www.stackone.com/.well-known/security.txt returned 404.",
          "RDAP for stackone.com gives a registration date of 2013-06-25. The company was incorporated later, per its company number.",
          "status.stackone.com runs on incident.io and lists the Web Dashboard, the API (US, EU and UK) and the Connectors Hub.",
          "trust.stackone.com, which the terms cite for the security policy and the sub-processor list, answered our reader with a bot check and was not read."
        ],
        "score": 88
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/stackone.json",
      "live": {
        "slug": "stackone",
        "probe": {
          "target": "https://mcp.stackone.com/mcp",
          "method": "mcp-initialize",
          "lastAt": "2026-10-10T02:07:26.369561075Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 377,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 112,
          "p95ms24h": 295,
          "samples24h": 107,
          "samples30d": 107,
          "days": [
            {
              "date": "2026-10-09",
              "probes": 85,
              "ok": 85
            },
            {
              "date": "2026-10-10",
              "probes": 22,
              "ok": 22
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.stackone.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-10-10T02:06:29.204045169Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "StackOneHQ/stackone-ai-node",
            "version": "v2.10.0",
            "released": "2026-07-27",
            "seenAt": "2026-10-09T17:21:48.091098138Z"
          },
          {
            "registry": "npm",
            "name": "@stackone/ai",
            "version": "2.10.0",
            "seenAt": "2026-10-09T17:21:45.859326927Z"
          },
          {
            "registry": "npm",
            "name": "@stackone/defender",
            "version": "0.8.3",
            "seenAt": "2026-10-09T17:21:46.919917579Z"
          },
          {
            "registry": "pypi",
            "name": "stackone-ai",
            "version": "2.10.1",
            "released": "2026-07-28",
            "seenAt": "2026-10-09T17:21:46.731430671Z"
          }
        ],
        "githubStars": 30,
        "npmWeekly": 277,
        "pypiWeekly": 120,
        "pages": [
          {
            "url": "https://www.stackone.com/changelog/",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-09T18:54:33.415845489Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "a8dc254bb424"
          },
          {
            "url": "https://www.stackone.com/pricing/",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-10-09T18:54:35.567295878Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "98687cfb089f"
          },
          {
            "url": "https://www.stackone.com/terms/privacy-policy/",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-09T18:54:37.551620202Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "011ecd948b67"
          },
          {
            "url": "https://www.stackone.com/terms/saas-terms/",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-09T18:54:39.532884111Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "393a890498df"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.stackone.com/mcp",
          "checkedAt": "2026-10-09T21:40:55.809059913Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-10-09T21:40:55.809059913Z"
        },
        "updatedAt": "2026-10-10T02:07:26.369561075Z"
      }
    },
    "facts": [
      {
        "a": "MCP server",
        "b": "MCP server",
        "name": "Kind"
      },
      {
        "a": "Merge API, Inc.",
        "b": "StackOne Technologies Limited",
        "name": "Vendor"
      },
      {
        "a": "https://ah-api.merge.dev/mcp",
        "b": "https://mcp.stackone.com/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP, HTTP",
        "b": "Streamable HTTP, HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Freemium",
        "b": "Freemium",
        "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 StackOne's SaaS Terms and Conditions. The Agent SDKs (`@stackone/ai`, `stackone-ai`) and the Defender package (`@stackone/defender`) are Apache-2.0",
        "name": "Licence"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "not listed",
        "b": "com.stackone/mcp",
        "name": "MCP registry"
      },
      {
        "a": "2026-10-05",
        "b": "2026-09-24",
        "name": "Last release"
      },
      {
        "a": "2026-09-09",
        "b": "2026-03-30",
        "name": "Terms last updated"
      },
      {
        "a": "2026-08-20",
        "b": "2023-12-01",
        "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": "not found in the text",
        "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": "30 stars, 277 npm/wk",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "Merge Agent Handler and StackOne score within a point of each other on agent readiness, 69.5 (B) and 69.1 (B). StackOne leads on reliability, agent ergonomics and maintenance \u0026 community.",
        "question": "Which is better for AI agents, Merge Agent Handler or StackOne?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do Merge Agent Handler and StackOne need an API key?"
      },
      {
        "answer": "Yes. Merge Agent Handler has a hosted endpoint at https://ah-api.merge.dev/mcp and StackOne at https://mcp.stackone.com/mcp.",
        "question": "Can an agent call Merge Agent Handler and StackOne without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Security \u0026 auth, 83 against 69",
          "Payments \u0026 pricing, 55 against 38"
        ],
        "also": null,
        "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, 80 against 59",
          "Agent ergonomics, 75 against 68",
          "Maintenance \u0026 community, 84 against 69"
        ],
        "also": null,
        "goodFor": "A company that wants one governed MCP endpoint for staff agents across business systems, and product teams embedding per-customer connections with HR, recruiting and CRM coverage.",
        "slug": "stackone",
        "watchFor": "Session token URLs (`https://api.stackone.com/mcp?token=...`) put the credential in the query string, cover one linked account and expire after one year by default"
      }
    ],
    "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-stackone.json",
        "title": "Composio (API + MCP) vs StackOne",
        "url": "https://www.anchorterminal.com/compare/composio-rube-vs-stackone"
      },
      {
        "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-unified-to-mcp.json",
        "title": "Merge Agent Handler vs Unified.to MCP Server",
        "url": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-unified-to-mcp"
      },
      {
        "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-stackone.json",
        "title": "One vs StackOne",
        "url": "https://www.anchorterminal.com/compare/one-vs-stackone"
      },
      {
        "json": "https://www.anchorterminal.com/compare/smithery-vs-stackone.json",
        "title": "Smithery vs StackOne",
        "url": "https://www.anchorterminal.com/compare/smithery-vs-stackone"
      },
      {
        "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/stackone-vs-zapier-mcp.json",
        "title": "StackOne vs Zapier MCP (agent actions)",
        "url": "https://www.anchorterminal.com/compare/stackone-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-stackone.json",
        "title": "letme vs StackOne",
        "url": "https://www.anchorterminal.com/compare/letme-vs-stackone"
      }
    ],
    "scores": [
      {
        "by": 21,
        "edge": "stackone",
        "key": "reliability",
        "merge-agent-handler": 59,
        "name": "Reliability",
        "stackone": 80,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 2,
        "edge": "merge-agent-handler",
        "key": "schema",
        "merge-agent-handler": 80,
        "name": "Schema \u0026 documentation",
        "stackone": 78,
        "weight": 13
      },
      {
        "by": 7,
        "edge": "stackone",
        "key": "ergonomics",
        "merge-agent-handler": 68,
        "name": "Agent ergonomics",
        "stackone": 75,
        "weight": 13
      },
      {
        "by": 14,
        "edge": "merge-agent-handler",
        "key": "security",
        "merge-agent-handler": 83,
        "name": "Security \u0026 auth",
        "stackone": 69,
        "weight": 14
      },
      {
        "by": 17,
        "edge": "merge-agent-handler",
        "key": "payments",
        "merge-agent-handler": 55,
        "name": "Payments \u0026 pricing",
        "stackone": 38,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 15,
        "edge": "stackone",
        "key": "maintenance",
        "merge-agent-handler": 69,
        "name": "Maintenance \u0026 community",
        "stackone": 84,
        "weight": 7
      },
      {
        "by": 2,
        "edge": "merge-agent-handler",
        "key": "transparency",
        "merge-agent-handler": 71,
        "name": "Transparency \u0026 trust",
        "stackone": 69,
        "weight": 7
      }
    ],
    "summary": "Merge Agent Handler and StackOne score within a point of each other on agent readiness, 69.5 (B) and 69.1 (B). StackOne leads on reliability, agent ergonomics 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.",
      "stackone": "StackOne's MCP server signs each person in with OAuth, lets them grant individual accounts and actions, and by default exposes two search and execute tools in place of the full catalogue. Session token URLs carry the credential in the query string for a year by default, and the Consumption Schedule and pricing page disagree on whether failed calls are billed."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-stackone",
    "json": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-stackone.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-stackone.md",
    "slim": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-stackone.min.md"
  },
  "markdown": "Merge Agent Handler and StackOne score within a point of each other on agent readiness, 69.5 (B) and 69.1 (B). StackOne leads on reliability, agent ergonomics 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- StackOne: grade B, 69.1/100, rank #198 of 950. Markdown https://www.anchorterminal.com/tools/stackone.md · JSON https://www.anchorterminal.com/api/v1/tools/stackone.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 69\n- Payments \u0026 pricing, 55 against 38\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### StackOne (B)\n\nGood for: A company that wants one governed MCP endpoint for staff agents across business systems, and product teams embedding per-customer connections with HR, recruiting and CRM coverage.\n\nAhead on:\n- Reliability, 80 against 59\n- Agent ergonomics, 75 against 68\n- Maintenance \u0026 community, 84 against 69\n\nWatch for: Session token URLs (`https://api.stackone.com/mcp?token=...`) put the credential in the query string, cover one linked account and expire after one year by default\n\n\n## Score by category\n\n| Category | Weight | Merge Agent Handler | StackOne | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 59 | 80 | StackOne +21 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 80 | 78 | Merge Agent Handler +2 |\n| Agent ergonomics | 13% (16.2 this run) | 68 | 75 | StackOne +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 83 | 69 | Merge Agent Handler +14 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 55 | 38 | Merge Agent Handler +17 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 69 | 84 | StackOne +15 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 71 | 69 | Merge Agent Handler +2 |\n| Negative events | ≤15 | 0 | -2 | |\n| **Total** | | **69.5 · B** | **69.1 · B** | |\n\n## Facts side by side\n\n| Fact | Merge Agent Handler | StackOne |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Merge API, Inc. | StackOne Technologies Limited |\n| Hosted endpoint | `https://ah-api.merge.dev/mcp` | `https://mcp.stackone.com/mcp` |\n| Transports | Streamable HTTP, HTTP | Streamable HTTP, HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\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 StackOne's SaaS Terms and Conditions. The Agent SDKs (`@stackone/ai`, `stackone-ai`) and the Defender package (`@stackone/defender`) are Apache-2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `com.stackone/mcp` |\n| Last release | 2026-10-05 | 2026-09-24 |\n| Terms last updated | 2026-09-09 | 2026-03-30 |\n| Privacy policy last updated | 2026-08-20 | 2023-12-01 |\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 | not found in the text |\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 | 30 stars, 277 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**StackOne.** StackOne's MCP server signs each person in with OAuth, lets them grant individual accounts and actions, and by default exposes two search and execute tools in place of the full catalogue. Session token URLs carry the credential in the query string for a year by default, and the Consumption Schedule and pricing page disagree on whether failed calls are billed.\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### StackOne\n\n1. Send `Accept: application/json,text/event-stream` on every MCP request to `https://api.stackone.com/mcp`, by POST only. Without it the server answers 406\n2. In `search_execute` mode call `{provider}_search_actions` first and pass the returned `action_id` to `{provider}_execute_action`. Never hardcode action ids\n3. Pass the API key as the Basic auth username with an empty password, and name the linked account in `x-account-id`\n4. On 429 or 408 wait the seconds given in `Retry-After`. StackOne has already retried a provider's 429 up to five times within a 60-second request lifetime\n5. On 412 read `errorCode` and `details.statusReasons`. `AccountErrorStatus` needs a person to re-authenticate the linked account\n\n## Questions\n\n### Which is better for AI agents, Merge Agent Handler or StackOne?\n\nMerge Agent Handler and StackOne score within a point of each other on agent readiness, 69.5 (B) and 69.1 (B). StackOne leads on reliability, agent ergonomics and maintenance \u0026 community.\n\n### Do Merge Agent Handler and StackOne 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 StackOne without installing anything?\n\nYes. Merge Agent Handler has a hosted endpoint at https://ah-api.merge.dev/mcp and StackOne at https://mcp.stackone.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/merge-agent-handler-vs-stackone.json, and with the fewest tokens: https://www.anchorterminal.com/compare/merge-agent-handler-vs-stackone.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"merge-agent-handler\", \"b\": \"stackone\"}`. From a terminal: `anchor compare merge-agent-handler stackone`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/merge-agent-handler.json and https://www.anchorterminal.com/api/v1/tools/stackone.json\n\n## Other comparisons with Merge Agent Handler or StackOne\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 StackOne](https://www.anchorterminal.com/compare/composio-rube-vs-stackone.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 Unified.to MCP Server](https://www.anchorterminal.com/compare/merge-agent-handler-vs-unified-to-mcp.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 StackOne](https://www.anchorterminal.com/compare/one-vs-stackone.md)\n- [Smithery vs StackOne](https://www.anchorterminal.com/compare/smithery-vs-stackone.md)\n- [StackOne vs Unified.to MCP Server](https://www.anchorterminal.com/compare/stackone-vs-unified-to-mcp.md)\n- [StackOne vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/stackone-vs-zapier-mcp.md)\n- [letme vs Merge Agent Handler](https://www.anchorterminal.com/compare/letme-vs-merge-agent-handler.md)\n- [letme vs StackOne](https://www.anchorterminal.com/compare/letme-vs-stackone.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 StackOne",
        "url": ""
      }
    ],
    "description": "Merge Agent Handler and StackOne score within a point of each other for app automation, 69.5 and 69.1 out of 100. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Merge Agent Handler B 69.5",
      "StackOne B 69.1",
      "scores"
    ],
    "h1": "Merge Agent Handler vs StackOne",
    "image": "https://www.anchorterminal.com/assets/og/compare-merge-agent-handler-vs-stackone.png",
    "path": "/compare/merge-agent-handler-vs-stackone",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Merge Agent Handler vs StackOne for AI agents (2026) | Anchor Terminal",
    "toc": null,
    "updated": "2026-10-09",
    "url": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-stackone"
  },
  "tokens": {
    "markdown": 2400,
    "slim": 730
  },
  "version": 1
}