WritersLogic legal-ip agents
REMOTE · AGENTS.WRITERSLOGIC.COM
Patent prior art, design-around, patent strategy, legal-citation verification.
Available components
Last scanned (22 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability54
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1836 tokens (~262/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 15 Nov 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://agents.writerslogic.com/mcp/legal-ip
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=writerslogic.com | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 802305745c0c9ae0139546a9e543dd74 |
| SANs: writerslogic.com, agents.writerslogic.com, *.agents.writerslogic.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of agents.writerslogic.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| writerslogic.com. | DS published | 2371 | 13 | Verified |
| agents.writerslogic.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agents.writerslogic.com/mcp/legal-ip | Verified | 200 | |
| http (plaintext) | http://agents.writerslogic.com/mcp/legal-ip | HTTPS enforced | 301 | https://agents.writerslogic.com/mcp/legal-ip |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
form-finder ~208
Government Form & Procedure Finder (California, San Diego) — Given a plain-language situation (for example a city took belongings in an encampment sweep, a parking ticket, a contractor overcharge), returns the official government or court forms and procedures that apply, each with its official URL, issuer, how and where to file, fee, and the filing deadline computed from a reference date where a rule sets one. Covers California statewide plus the City and C
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Reference date YYYY-MM-DD, taken as the trigger of each forward deadline rule (incident date, citation date, notice mailing date); each match names its trigger. Rules that count back from a future ev… |
| jurisdiction | object | yes | – |
| max_results | integer | – | Default 5. |
| situation | string | yes | Plain-language description of what happened or what the person wants to do. |
No output schema declared.
No examples provided.
legal-cite-verifier ~245
Legal citation and quotation verifier (US case law) — Extracts US reporter citations from a brief (U.S., S. Ct., L. Ed., F., F.2d, F.3d, F.4th, F. Supp., state and regional reporters) and checks each against Harvard's Caselaw Access Project and, when the operator has configured a token, the CourtListener Citation Lookup API. Reports FOUND, MISMATCH (case name, year or circuit differs), NOT_FOUND, AMBIGUOUS, or UNCHECKED with the reason, and never mar
| Name | Type | Req | Description |
|---|---|---|---|
| check_propositions | boolean | – | Default false. Runs one optional model call that may only point at a verified passage. |
| citations | array | – | Citations to check instead of, or in addition to, text. |
| max_citations | integer | – | Distinct reporter citations to check. Default 40. |
| propositions | array | – | – |
| quotes | array | – | Quotations to find verbatim in the cited opinion. |
| text | string | – | Brief or memo text. Citations and their case names, court and year are extracted from it. |
No output schema declared.
No examples provided.
patent-design-around ~231
Patent Design-Around & Freedom-to-Operate Architect — Paste patent claims or give a patent number. Splits the independent claims into lettered limitations in code, charts your product against each one (literal and doctrine of equivalents), scores claims under the all-elements rule, and proposes 3 engineering design-arounds that each remove a limitation of every independent claim, checked in code. Leads with a decision and optional dollar exposure. A
| Name | Type | Req | Description |
|---|---|---|---|
| annualRevenueUsd | number | – | Annual revenue that depends on the product; sizes the dollar exposure in the headline. |
| assumedRoyaltyPct | number | – | Assumed running royalty as a percent of revenue, for the exposure illustration. |
| jurisdiction | string | – | Defaults to US. |
| patentClaimsText | string | – | Numbered claims (at least the independent claims). Optional when patentNumber is given: the claims are then read from Google Patents. |
| patentNumber | string | – | Publication number such as US7629993B2. Used to read the claims from Google Patents when patentClaimsText is omitted. |
| proposedProductDescription | string | yes | – |
No output schema declared.
No examples provided.
patent-strategy ~279
Patent Strategy Pack — Both sides of a blocking patent in one call: pre-priority-date prior art charted against every claim element, and an all-elements freedom-to-operate map with three engineering design-arounds. Runs prior-art-invalidator ($1.00) + patent-design-around ($2.00) in one paid call for 20% less than buying them separately. Charged only when every member succeeds.
| Name | Type | Req | Description |
|---|---|---|---|
| annualRevenueUsd | number | – | Annual revenue that depends on the product; sizes the dollar exposure in the headline. |
| assumedRoyaltyPct | number | – | Assumed running royalty as a percent of revenue, for the exposure illustration. |
| jurisdiction | string | – | Defaults to US. |
| patentClaimsText | string | – | Numbered claims (at least the independent claims). Optional when patentNumber is given: the claims are then read from Google Patents. |
| patentNumber | string | – | Publication number such as US7629993B2. Used to read the claims from Google Patents when patentClaimsText is omitted. |
| priorityDate | string | – | Earliest effective filing/priority date, YYYY-MM-DD. Only works published strictly before it count. Optional when patentNumber is given; a supplied date wins over the Google Patents date and a disagr… |
| proposedProductDescription | string | yes | – |
No output schema declared.
No examples provided.
precedent-search ~232
Case-law precedent search (CourtListener, US) — Finds US court opinions most on point for a legal question or fact pattern: searches CourtListener's case-law index (optionally limited to courts and filing dates), reads the top opinions, and returns the best matches with a holding passage verified verbatim against the opinion text, plus citation, court, date, precedential status and a source hash. A second skeptical pass flags matches that look
| Name | Type | Req | Description |
|---|---|---|---|
| courts | array | – | CourtListener court ids such as "scotus", "ca9", "cal", "calctapp". Omit to search all courts. |
| filed_after | string | – | Earliest filing date, YYYY-MM-DD. |
| filed_before | string | – | Latest filing date, YYYY-MM-DD. |
| include_excerpts | boolean | – | Default true. When false, the holding passage text is omitted from the output (quote_verified and quote_offset are still reported). |
| max_results | integer | – | Default 5. |
| question | string | yes | The legal issue and key facts. Quote a phrase to require it verbatim in the search. |
No output schema declared.
No examples provided.
prior-art-invalidator ~273
Global Prior-Art Patent Invalidator — Screens a patent's claims against scholarly literature published before the priority date (arXiv, OpenAlex, Europe PMC, Crossref, HAL, J-STAGE; English, Chinese, Japanese, German; not patent databases). Give claims plus a priority date, or a patent number to read them from Google Patents. Claims are split into elements in code; every claim-chart quote is verified verbatim against the title or abst
| Name | Type | Req | Description |
|---|---|---|---|
| patentClaimsText | string | – | Claims to attack, numbered as in the patent (e.g. "1. A method ..."). Optional when patentNumber is given: the independent claims are then read from Google Patents. A dependent claim is charted with… |
| patentNumber | string | – | Publication number such as US7629993B2. Claims, priority date and cited art are read from Google Patents when the claims or the date are omitted, and the date is cross-checked otherwise. Required unl… |
| priorityDate | string | – | Earliest effective filing/priority date, YYYY-MM-DD. Only works published strictly before it count. Optional when patentNumber is given; a supplied date wins over the Google Patents date and a disagr… |
No output schema declared.
No examples provided.
regulatory-change-brief ~315
Regulatory Change Brief (Federal Register, EDGAR, Dockets) — Given an industry or topic and optional agencies, CFR parts, terms and companies, pulls recent US regulatory changes from official free sources: Federal Register final and proposed rules (with effective dates, comment deadlines and official URLs), SEC EDGAR 8-K items and other filings for named companies, and CourtListener dockets and opinions when the operator has a token. Days remaining are comp
| Name | Type | Req | Description |
|---|---|---|---|
| agencies | array | – | Agency names, acronyms or Federal Register slugs, e.g. "SEC", "Environmental Protection Agency". |
| cfr_parts | array | – | CFR parts, e.g. "17 CFR 240" or "40 CFR 60". |
| companies | array | – | Company names, tickers or CIKs whose recent SEC filings (8-K items, 10-K/Q) to list. |
| focus | string | – | Weights ranking and the impact assessment toward operations, reporting or enforcement. |
| industry | string | – | Industry or topic, e.g. "community banks offering consumer credit". Used to plan searches and to judge impact. |
| sic_codes | array | – | SIC codes; industry context only, registrants are not enumerated by SIC. |
| terms | array | – | Federal Register search phrases, e.g. "data breach notification". |
| window_days | integer | – | Publication window ending today, 1 to 180 days (default 30). Proposed rules published earlier whose comment period is still open are also included. |
No output schema declared.
No examples provided.
How do I install the WritersLogic legal-ip agents MCP server?
WritersLogic legal-ip agents is a hosted endpoint at https://agents.writerslogic.com/mcp/legal-ip, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agents.writerslogic.com
claude mcp add --transport http com-writerslogic-agents-writerslogic-legal-ip 'https://agents.writerslogic.com/mcp/legal-ip'
What is the WritersLogic legal-ip agents MCP server?
WritersLogic legal-ip agents is an MCP server listed in the public MCP registry as com.writerslogic.agents/writerslogic-legal-ip. Patent prior art, design-around, patent strategy, legal-citation verification. This page covers its hosted endpoint (https://agents.writerslogic.com/mcp/legal-ip).
Is the WritersLogic legal-ip agents MCP server safe to use?
WritersLogic legal-ip agents scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the WritersLogic legal-ip agents MCP server expose?
WritersLogic legal-ip agents exposes 7 tools: patent-design-around, legal-cite-verifier, prior-art-invalidator, regulatory-change-brief, patent-strategy, and 2 more. Their descriptions and schemas cost roughly 1,783 tokens of context every time the server is loaded.
Does the WritersLogic legal-ip agents MCP server require authentication?
No. We connected to WritersLogic legal-ip agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the WritersLogic legal-ip agents MCP server still maintained?
WritersLogic legal-ip agents is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the WritersLogic legal-ip agents MCP server?
VerifyMCP ran 12 checks on WritersLogic legal-ip agents, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about WritersLogic legal-ip agents: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.