Solve Intelligence
Search global patent literature, non-patent literature, case law and SEP standards from an AI agent. Nine read-only tools; Solve states drafting, prosecution and claim charting stay in its own platform. One undifferentiated OAuth scope.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Solve Intelligence via MCP
https://api.solveintelligence.com/mcp/Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Solve Intelligence Tools & Capabilities (9)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- One OAuth scope covers everything. The RFC 9728 descriptor at
https://api.solveintelligence.com/.well-known/oauth-protected-resourceadvertises exactlyoffline_accessandmcp:ask_solve. Only the second governs data, and it is undifferentiated: consent cannot grant patent search without also granting legal-text and standards retrieval. There is no write scope to withhold, which is the reassuring half — but there is also no boundary between the nine reads. Compare Patlytics, which offers two typed read scopes. mcp:ask_solvenames a verb no tool carries. A scope naming an operation absent from the tool list is normally evidence of a surface you have not seen. Here the mismatch reads as a product-level grant name — "ask Solve" is how Solve markets its Copilot — rather than a hidden operation, because the scope verb is a read and the tools are all reads. We could not rule out the alternative, because the endpoint would not enumerate itself to us.- The documentation URL in Anthropic's directory is not publicly readable.
https://api.solveintelligence.com/guide/mcp/intro/returns HTTP 307 tohttps://copilot.solveintelligence.com/guide, which serves a 4,752-byte single-page-app shell identically for every guide path. The app's own bundle shows the guide rendered in an iframe under an/_authenticated/guide/$route pointing back at the API host. The real guide is behind sign-in. This page is built from Solve's public blog posts instead. - Solve publishes no tool names, so a rename would be invisible. We diffed the directory's nine names against Solve's statement of what the connector excludes — a semantic match against a negative list, not a literal-string match in both directions. Nothing contradicts the listing, and nothing would reveal a silent rename or a quietly added tool.
- No tool schemas or safety annotations could be read. The endpoint returned 401 to an anonymous request on 2026-08-23, so no parameter-level detail is published here — including the parameter-level check that would rule a dispatcher in or out.
- No dynamic client registration. Solve's authorization server declares no
registration_endpoint. Clients requiring DCR-based OAuth will need credentials supplied another way. - Solve documents the accuracy problem in its own field, plainly. Its writing on AI in patent prosecution states that anyone presenting AI-assisted content to the USPTO must reasonably review it, that courts have already sanctioned attorneys over AI-hallucinated citations, and that the EPO Guidelines hold a representative responsible for a document's content regardless of the tool used. It names automation bias as its fifth risk. Verify every citation the agent returns.
- Prosecution-history estoppel makes plausible output expensive. Solve notes that an argument characterising an invention more narrowly than necessary can permanently surrender claim scope, and that because it sounds reasonable the error can survive review and surface years later. That risk attaches to what you file, not to what this connector returns — but the connector is a source of the text.
- Open web reach is your agent's, not Solve's. Solve's infringement-detection example combines patent analysis with open web research. No tool among the nine fetches a web page.
- Access requires an existing subscription and an admin. Only Solve organization administrators can enable the integration, and both a Solve and a Claude subscription are required.
- Whether anything is metered per call is unresolved. Solve publishes no pricing page and no rate, its terms bill by subscription in advance, and no tool can report a balance. We could not establish whether an Order Form may meter search volume.
Frequently asked questions
No. All nine tools carry read verbs — search, get, list, read, grep, lookup — and none writes to a document, a docket or a patent office. Solve states in its launch announcement that customers wanting its drafting, prosecution and claim charting tools will find those inside the Solve platform, not through this connector.
Because the description covers what Claude can do with retrieved material, not what the connector writes. Anthropic's directory one-liner reads search, draft, and chart patents, and its permissions field for this same entry reads Read. Any drafting happens as text in the Claude conversation. Nothing lands in Solve.
Solve publishes no per-search rate, no credit balance and no public pricing page. Its terms bill a subscription fee in advance against an Order Form rather than by metered usage, and no tool among the nine can report a balance or quota. So the marginal cost of a call is unpredictable from outside your contract.
Two, and only one governs data. The server's RFC 9728 descriptor and its 401 challenge both advertised offline_access and mcp:ask_solve on 2026-08-23. Because a single scope covers all nine tools, consent cannot separate public patent search from legal research or standards retrieval. It is one grant, all or nothing.
Existing Solve customers whose organization administrator has enabled it. Solve states the integration requires active subscriptions to both Solve Intelligence and Claude, and that only Solve organization administrators can enable it for their users. Solve also recommends obtaining IT approval before connecting. There is no self-serve path from the connector.
No. The documentation URL Anthropic publishes returns HTTP 307 to an authenticated single-page app whose guide is rendered in an iframe behind sign-in, verified on 2026-08-23. Solve's public launch blog post carries the connector detail instead, and it is what this page is built from.
Whatever you put in a Claude conversation. Solve states that when using Solve through Claude, security and data locality depend on your own Claude subscription and Anthropic's policies rather than Solve's infrastructure alone. Solve separately warns that unpublished application material can raise export-control and foreign-filing-license problems.
Nothing we found says it can. The nine tools name patents, non-patent literature, legal texts and standards — all external corpora — and none names a document, project, matter or workspace object. Solve publishes no schema for these tools, so treat this as the tool names' scope rather than a guarantee.
Sources
- Solve Intelligence blog, "Solve Intelligence MCP server now available in Claude" (retrieved 2026-08-23). The connector's corpora, example prompts, admin requirement and platform-versus-connector boundary come from here. · retrieved 2026-08-23
- Solve Intelligence blog, "Solve Intelligence, Powered by Claude" (retrieved 2026-08-23). Source for what the Solve platform does that the connector does not. · retrieved 2026-08-23
- Solve Intelligence blog, "Why Patent Practice Needs Purpose-Built AI: Reflections from Code with Claude" (retrieved 2026-08-23) · retrieved 2026-08-23
- Solve Intelligence blog, "The Honest Risks of Using AI in Patent Prosecution" (retrieved 2026-08-23). Source for the USPTO and EPO review duties, export control, estoppel and automation bias. · retrieved 2026-08-23
- Solve Intelligence Terms of Service (retrieved 2026-08-23). Source for the subscription-in-advance billing model. · retrieved 2026-08-23
- Solve Intelligence
robots.txt, which explicitly allows ClaudeBot, andsitemap.xml(224 URLs, no pricing page) — · (retrieved 2026-08-23) · retrieved 2026-08-23 - Anthropic's nominated documentation URL (probed 2026-08-23; HTTP 307 to an authenticated app, no readable content) · retrieved 2026-08-23
- Live OAuth posture check: anonymous initialize returned HTTP 401 with a
WWW-Authenticatebearer challenge; RFC 9728 metadata athttps://api.solveintelligence.com/.well-known/oauth-protected-resource; authorization server metadata athttps://api.solveintelligence.com/auth/.well-known/openid-configuration(2026-08-23) · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Solve Intelligence support — <mailto:support@solveintelligence.com> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Data & Research
- Developer
- Solve Intelligence
- Tools
- 9
- Domain
- api.solveintelligence.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.