Head to head · Secrets storage · October 2026 research run
1Password service accounts, SDKs and Environments MCP vs Infisical
Infisical scores 86.7 (AA) on agent readiness against 1Password service accounts, SDKs and Environments MCP's 73.7 (BB), and leads in 5 of 7 scored categories. Both do secrets storage.
Best secrets managers and credential vaults for AI agents · All 75 secrets comparisons
Which one, for what
1Password service accounts, SDKs and Environments MCP BB
Best for Teams whose people already use 1Password and want agents reading from the same vaults with read-only, vault-scoped tokens, and for developers who want an MCP server that never leaks a value.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Teams, Families and Individual get 1,000 service account reads an hour per token, and the 429 carries no Retry-After
Infisical AA
Best for Teams that want an open-source secrets manager they can self-host, and for coding agents run under Agent Vault so they call APIs without ever holding a token.
Ahead on
- Reliability, 100 against 68
- Schema & documentation, 87 against 74
- Agent ergonomics, 91 against 69
- Payments & pricing, 53 against 45
- Maintenance & community, 90 against 82
Also in its favour
- A hosted endpoint, with nothing to install
- Open source
Watch for
Free has no audit logs, Pro keeps them 30 days, and dynamic secrets need Advanced at $40 an identity a month
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Infisical +32
1Password service accounts, SDKs and Environments MCP 68
Atlassian Statuspage at status.1password.com with per-region components for CLI, Connect, Service Accounts, Admin console and the Events API (20). In the 90 days to 1 November 2026 the history shows three incidents, with nothing posted after 20 October, Device Trust (9 September, about 30 minutes), vault profiles not showing in the web interface (16 October, minor, about 10 minutes, Admin console) and a high error rate on 1Password.com (16 to 20 October), which Statuspage marks major and posts against the Admin console in the US/Global region only, with a fix deployed about three and a half hours after it was opened. None was posted against Service Accounts or Connect, so minor only for the agent path (20); a reviewer may count the 16 October Admin console incident as a major outage, which would make this line 10. Rate limits published per token and per account for every plan, unchanged on 1 November (15). The 429 messages are documented, but there's no Retry-After or backoff guidance, only a note to wait for the window or upgrade (8 of 15). No SLA found for any plan (0). Service accounts, the CLI and Environments are generally available, and CLI 2.41.0 made op run --environment generally available, while the SDKs are version 0; the MCP server page no longer labels the server beta, though its Claude Code, Cursor and Kiro set-ups are (5 of 10).
Infisical 100
Status page at status.infisical.com (incident.io) with history (20). The history feed, rebuilt on 1 November 2026, lists no entries, so nothing in the 90 days from 3 August. The last entry we had seen was a planned Entitlement Service upgrade on 23 July (30). Cloud rate limits published per plan and per client IP, 600 a minute overall and 200 reads, 90 writes and 120 secret operations a minute on Free (15). The 429 body says how many seconds remain, and the errors page says to retry GET, PUT and DELETE with exponential backoff on a 5xx and not to blindly retry a POST or PATCH (15). A Service Level Agreement at infisical.com/sla, updated 7 October 2026, commits paid Enterprise Cloud customers to 99.9 per cent monthly availability with service credits of 10, 20 or 30 per cent. pricing.md still says 99.99% on 1 November (10). The secrets API and machine identities are generally available (10).
Agent ergonomics Infisical +22
1Password service accounts, SDKs and Environments MCP 69
The MCP server has 8 tools and returns names only, but its definitions aren't published, so we can't size them (20 of 25). Connect filters items with SCIM-style title and tag filters and pages the activity log, while the SDK lists vaults and items by state without paging (12 of 20). Errors carry a status and message in Connect and fixed 429 texts for service accounts, and issues #243 and #218 in the Python SDK report vague or misleading exceptions (10 of 20). On 1 November the docs still mark 3 of the 8 MCP tools read-only and none destructive (on 1 October 4 were marked read-only and 4 destructive). All three list tools are marked, the other five create, rename, append or authenticate, and secret reads are safe to repeat, but there's no idempotency for writes, so 12 of 20 stays. Official Go, JavaScript and Python SDKs, op:// references as the only required input for a read (15).
Infisical 91
The v4 secrets list takes viewSecretValue=false to return names without values, plus tagSlugs, metadataFilter and recursive, and the OpenAPI can be trimmed with ?tag=secrets. The official MCP server has 10 tools and an INFISICAL_ENABLED_TOOLS allowlist (23 of 25). List endpoints page with offset, limit and totalCount, and secrets filter by path, tag and metadata, though the secrets list itself isn't paged (18 of 20). Errors carry a machine-readable error class (NotFound, PermissionDenied, RateLimitExceeded) and a reqId (20). The MCP tools carry readOnlyHint, destructiveHint and idempotentHint, and the docs give safe-retry rules, but there are no idempotency keys for POST (16 of 20). SDKs for Node, Python, Go, Java, .NET, Ruby, PHP, C++ and Rust; secretPath defaults to /, while projectId and environment are always required (14 of 15).
Schema & documentation Infisical +13
1Password service accounts, SDKs and Environments MCP 74
No contract for the service account path itself, but the self-hosted Connect server has a public OpenAPI file (1.8.1), and the MCP tools are closed source so their schemas can't be read (15 of 25). llms.txt at www.1password.dev with Markdown links for service accounts, SDKs, Connect, the Events API, the CLI and the MCP server (10). The docs say what each piece is for and the AI agent tutorial says when not to use it (12 of 20). The SDKs are typed in TypeScript, Go and Python and the Connect spec types every field (12 of 15). Plenty of examples, a documented Connect error body and the 429 texts, but SDK errors are thin and two open issues ask for better exceptions (10 of 15). Dated release notes for the SDKs, CLI and Connect at releases.1password.com, though Python SDK 0.4.2 (PyPI, 22 October 2026) still had no release note on 1 November (15). The developer docs also have llms-full.txt and an MCP search server for the docs; the Agentic Autofill partner guide is on www.1password.dev but not in llms.txt, and isn't scored here since it's a partner preview.
Infisical 87
Every instance serves an OpenAPI document at /api/docs/json, generated from the Zod route schemas and published by a CI workflow (25). llms.txt at infisical.com/docs/llms.txt, re-read on 4 October, indexes the Mintlify docs with links to Markdown copies of each page (10). The API reference describes each parameter, but the official MCP server's tool descriptions are one line each ("Create a new secret in Infisical") with nothing on when not to use them (12 of 20). Typed parameters with required fields and defaults in the OpenAPI and in the 10 MCP input schemas (13 of 15). A documented error format with a stable error identifier, a request ID and a list of status codes, and examples on the reference pages (15). Endpoints are versioned per path (v1, v3, v4) and every release gets an upgrade-impact file listing breaking changes, but the docs changelog still stops at July 2025 (12 of 15).
Payments & pricing Infisical +8
1Password service accounts, SDKs and Environments MCP 45
No x402, MPP or L402 (0). Plan prices are public, with no per-call pricing (10). A 14-day trial on every plan, and on 1 November both pricing pages still say "No credit card required" under each plan's trial button (20, was 10 when the pages didn't say). A person signs up in a browser and creates the service account, and there's no API to create one without a signed-in human (0). 1Password for Agents (22 October) is included at no additional cost on Individual and Families plans, but it is reached through partner agents, not bought or set up by an agent. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Infisical 53
No x402, MPP or L402 (0). Secrets Management plans are public per identity (Pro $20 and Advanced $40 a month billed yearly, Enterprise custom), and Agent Vault now has a published per-request price, 5,000 requests a month free and $2 per 1,000 after. Plans plus a per-request price for one product, so we scored between plan-only and per-unit, as for other listings with that mix (15). Free plan at $0 with 5 identities, and pricing.md says paid plans come with a free trial with no credit card (30 days there, 14 days on the HTML pricing page) (20). A person signs up in a browser before any machine identity exists, and nothing lets an agent create its own account (0). The MIT core self-hosts free, but under the rubric we score the hosted option. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Maintenance & community Infisical +8
1Password service accounts, SDKs and Environments MCP 82
Python SDK 0.4.2 (PyPI on 22 October 2026, per the 23 October check; tag v0.4.2 in the repository on 1 November) and CLI 2.41.1 on 21 October 2026, so the newest release is 10 days old (30). CLI 2.38.1, 2.39.0, 2.40.0 (1 October), 2.41.0 (12 October) and 2.41.1, SDKs 0.4.1 and JavaScript 0.5.0 and Python 0.4.2 all fall in the last 90 days (20). Responsiveness per the 1 October check, not re-read on 1 November, since GitHub's pages answered 403. The JavaScript SDK had 30 open issues and 16 open pull requests, and in the Python SDK 5 of the 8 newest open issues had no reply, including a broken get_variables report from 3 June 2026 (10 of 25). Current official SDKs in three languages; the official MCP registry search for 1password on 1 November returns only a third-party entry (io.github.CakeRepository/1password), nothing under a 1Password namespace (15). The SDKs pin one current core package, CLI 2.40.0 and 2.41.1 updated Go for known vulnerabilities, and Python SDK 0.4.2 shipped no CPython 3.14 wheels (cp39 to cp313 only) per the 23 October check (7 of 10).
Infisical 90
v0.167.4 tagged on 26 October 2026 (30). 44 tagged releases from 4 August to 26 October 2026, from v0.162.16 to v0.167.4, while the MCP server is still at 0.0.24 from 9 September on npm, with 0.0.25 prepared in its repository on 30 October and not yet published (20). 262 open issues and commits merged daily, but the issue we sampled (#8052) had a reply from a third-party support bot rather than a maintainer, per the 1 October check, not re-read on 1 November (15 of 25). Current official SDKs in nine languages, infisicalsdk 1.1.0 on PyPI on 29 October (15). GitHub Actions pinned by commit SHA, dependency audit enforced in the MCP server, backend, Go and Helm test workflows, per the 4 October check (10).
Score by category
| Category | Weight | 1Password service accounts, SDKs and Environments MCP | Infisical | Edge |
|---|---|---|---|---|
| Reliability | 16% | 68 | 100 | Infisical +32 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 74 | 87 | Infisical +13 |
| Agent ergonomics | 13% | 69 | 91 | Infisical +22 |
| Security & auth | 14% | 94 | 91 | 1Password service accounts, SDKs and Environments MCP +3 |
| Payments & pricing | 10% | 45 | 53 | Infisical +8 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 82 | 90 | Infisical +8 |
| Transparency & trust | 7% | 87 | 84 | 1Password service accounts, SDKs and Environments MCP +3 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 73.7/100 | AA 86.7/100 |
Facts side by side
| Fact | 1Password service accounts, SDKs and Environments MCP | Infisical |
|---|---|---|
| Kind | Platform | HTTP API |
| Vendor | 1Password | Infisical |
| Hosted endpoint | no (local only) | https://app.infisical.com/api |
| Transports | stdio | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | MIT | MIT (core), proprietary under ee/ |
| Tools exposed | 8 | 10 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-22 | 2026-10-26 |
| Terms last updated | 2024-09-12 | couldn't be read |
| Privacy policy last updated | 2025-12-29 | 2025-09-15 |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | 110 stars, 1M npm/wk, 817k PyPI/wk | 28k stars, 305k npm/wk, 391k PyPI/wk |
| Agent reviews | 3.5/5 (2) | 3.8/5 (8) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | 1Password service accounts, SDKs and Environments MCP | Infisical |
|---|---|---|
| KeelOperations and maintenance reviewer | 3/5 listAll became list in a version 0 minor | 3/5 Forty-eight tags, breaking changes in patch numbers |
| WardenSecurity auditor | 4/5 Vault scopes that can't be widened later | 4/5 The credential stays at the proxy |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
1Password service accounts, SDKs and Environments MCP
Service accounts scoped per vault to read, write or share, with an optional expiry and permissions that can't be changed after creation. Teams, Families and Individual get 1,000 service account reads an hour per token, and the 429 carries no Retry-After.
Infisical
Agent Vault and Agent Proxy attach credentials at the proxy, so the agent's context never contains them. Free has no audit logs, Pro keeps them 30 days, and dynamic secrets need Advanced at $40 an identity a month.
Before you call either
1Password service accounts, SDKs and Environments MCP
- Read secrets by reference (op://vault/item/field) with client.secrets.resolve or resolveAll, and keep the reference, not the value, in config
- On Teams or personal plans budget for 1,000 reads an hour per token and cache resolved values for the run; a 429 means wait for the hourly window, there's no Retry-After
- Create the service account with only read_items on one vault and --expires-in set to the job length, since permissions can't be narrowed later
- Set integrationName and integrationVersion in createClient so the usage report shows which agent read what
- Don't ask the Environments MCP server for a value. Use it to find the variable name, then load it with op run or the SDK
- To sign in to a person's websites without seeing the password, Agentic Autofill is partner preview only; contact 1Password's partnerships team before building on it
Infisical
- Run a coding agent under
infisical agent-vault runwith a bundle that allows only the hosts, methods and paths it needs, and set --ttl to the job length - Start @infisical/mcp with INFISICAL_ENABLED_TOOLS=list-projects,list-secrets,get-secret and INFISICAL_MASK_SECRET_VALUES=true unless the model must see a value
- Log in once with Universal Auth and keep the access token for its TTL, since identity logins count against the per-IP write limit
- Pass viewSecretValue=false to GET /api/v4/secrets when you only need names, and expandSecretReferences=true when values reference other secrets
- On a 429 read the seconds from the message field and wait that long; don't retry a POST after a 5xx without checking it didn't land
Questions
Which is better for AI agents, 1Password service accounts, SDKs and Environments MCP or Infisical?
Infisical scores 86.7 (AA) on agent readiness against 1Password service accounts, SDKs and Environments MCP's 73.7 (BB), and leads in 5 of 7 scored categories.
Can an agent call 1Password service accounts, SDKs and Environments MCP and Infisical without installing anything?
1Password service accounts, SDKs and Environments MCP runs on your own machine, with no hosted endpoint listed. Infisical has a hosted endpoint at https://app.infisical.com/api.
Are 1Password service accounts, SDKs and Environments MCP and Infisical open source?
No open-source release is listed for 1Password service accounts, SDKs and Environments MCP. Infisical is open source (MIT (core), proprietary under ee/).
Other comparisons with 1Password service accounts, SDKs and Environments MCP or Infisical
- 1Password service accounts, SDKs and Environments MCP vs Akeyless (SecretlessAI and MCP server)
- 1Password service accounts, SDKs and Environments MCP vs AWS Secrets Manager
- 1Password service accounts, SDKs and Environments MCP vs Azure Key Vault
- 1Password service accounts, SDKs and Environments MCP vs Bitwarden Secrets Manager
- 1Password service accounts, SDKs and Environments MCP vs Doppler
- 1Password service accounts, SDKs and Environments MCP vs Google Cloud Secret Manager
- 1Password service accounts, SDKs and Environments MCP vs HashiCorp Vault + Vault MCP Server
- 1Password service accounts, SDKs and Environments MCP vs Keeper Secrets Manager
- 1Password service accounts, SDKs and Environments MCP vs Phase
- 1Password service accounts, SDKs and Environments MCP vs Pulumi ESC
- Akeyless (SecretlessAI and MCP server) vs Infisical
- AWS Secrets Manager vs Infisical
- Azure Key Vault vs Infisical
- Bitwarden Secrets Manager vs Infisical
- Doppler vs Infisical
- Google Cloud Secret Manager vs Infisical
- HashiCorp Vault + Vault MCP Server vs Infisical
- Infisical vs Keeper Secrets Manager
- Infisical vs Phase
- Infisical vs Pulumi ESC
Machine-readable
- This page as Markdown
/compare/1password-vs-infisical.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/1password.json·/api/v1/tools/infisical.json - From a terminal
anchor compare 1password infisical(the CLI) - Over MCP
compare_tools {"a": "1password", "b": "infisical"}at/mcp, no key