WritersLogic business agents
REMOTE · AGENTS.WRITERSLOGIC.COM
Medical-bill audit, chargeback, contract terminator, lead enrichment, filing integrity.
Available components
Last scanned (12 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 95 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 21511 tokens (~226/item across 95 items; 95 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 Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 77% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "storage-charge-clock" implies "charge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 96 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 95 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
- “storage-charge-clock” reworded the description of “currency” cosmetic
- “storage-charge-clock” reworded the description of “freeCounting” cosmetic
- “storage-charge-clock” reworded the description of “freeDays” cosmetic
- “storage-charge-clock” reworded the description of “receivedOn” cosmetic
- “storage-charge-clock” reworded the description of “releasedOn” cosmetic
5 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 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 60
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/business
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/business | Verified | 200 | |
| http (plaintext) | http://agents.writerslogic.com/mcp/business | HTTPS enforced | 301 | https://agents.writerslogic.com/mcp/business |
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 →
medical-bill-auditor ~347
Medical Bill Upcoding & Overcharge Slasher — Paste an itemized hospital or physician bill and get a decision first: dispute it or not, the estimated dollars above a defensible price, and a dispute letter ready to send. Flags E/M upcoding, NCCI unbundling, duplicates and unit errors line by line, prices professional claims against the CMS physician fee schedule, checks the No Surprises Act self-pay dispute deadline, and lists the letter's pla
| Name | Type | Req | Description |
|---|---|---|---|
| accountNumber | string | – | – |
| billReceivedDate | string | – | Date the initial bill was received; used for the 120-day dispute deadline. |
| billText | string | – | Alternative to lineItems: paste the itemized bill, one line item per line, e.g. "99285 EMERGENCY DEPT VISIT LVL 5 1 $3,250.00". Lines with a CPT/HCPCS code and a dollar amount are read in code;… |
| claimType | string | – | Physician (CMS-1500) or hospital/facility (UB-04) bill. Medicare physician fee schedule benchmarks apply only to professional claims. |
| coverage | string | – | Determines which No Surprises Act protections can apply. |
| facilityName | string | – | – |
| facilityType | string | yes | – |
| goodFaithEstimateAmount | number | – | Good Faith Estimate received (self-pay). |
| lineItems | array | – | – |
| patientName | string | – | – |
| patientState | string | – | – |
| visitSummary | string | – | What actually happened: symptoms, duration, tests, treatment. |
No output schema declared.
No examples provided.
metar-parse ~142
METAR / SPECI decoder with flight category — Decodes up to 20 METAR or SPECI aviation weather reports (US and ICAO forms: wind with gusts and variable direction, visibility in statute miles or metres, CAVOK, RVR, present weather, cloud layers, temperature/dew point, altimeter, trend, RMK remarks) into structured fields and computes the FAA flight category (LIFR/IFR/MVFR/VFR). Every token it cannot decode is returned with its character offset
| Name | Type | Req | Description |
|---|---|---|---|
| claims | array | – | Optional claims to verify against the decoded report. |
| reports | array | yes | Reports to decode. |
No output schema declared.
No examples provided.
metered-price ~338
Tiered usage pricing: graduated or volume tiers, included quantity, package units, minimum charge — Prices a usage quantity against up to 50 tiers, graduated (each tier prices only its own units) or volume (the tier holding the whole quantity prices all of it), for an agent checking a usage bill or quoting a plan. Order of operations: subtract the included quantity, convert to billing packages (per N units, rounded up, down or not at all), price the tiers, add flat fees, apply the minimum charge
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | ISO 4217 alphabetic code, upper case. |
| exponent | integer | – | – |
| included | string | – | Free quantity subtracted before packaging and tiers (never below zero). |
| minimum | string | – | Minimum charge in major units, applied after the tiers. |
| mode | string | yes | – |
| packageRounding | string | – | How a partial package is billed when per > 1. Default up. |
| per | string | – | Units per billing package (default 1). Tiers are expressed in packages. |
| quantity | string | yes | Decimal string such as "-12.50" (up to 15 integer and 12 fraction digits). JSON numbers are not accepted: they are binary floats. |
| rounding | string | – | Final rounding to the minor unit. Default half-up. half-up: ties away from zero. half-down: ties toward zero. half-even: ties to the even neighbour. up: away from zero. down: toward zero. ceiling: to… |
| tiers | array | yes | – |
No output schema declared.
No examples provided.
minor-units ~128
ISO 4217 minor units: decimal amount to integer minor units and back — Converts up to 200 money amounts between decimal strings and integer minor units (cents, yen, fils) using the ISO 4217 exponent from the SIX Group list, for an agent about to send an amount to a payment API. Returns the exponent, the integer minor amount and the canonical decimal string; JPY is 0, KWD and BHD are 3, CLF is 4. An amount with more fraction digits than the currency allows fails with
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
naive-timestamp-hazard ~160
Which timestamps are anchored? Flags naive local times, zone abbreviations, date-only, epoch units and d/m ambiguity — Classifies up to 200 timestamp strings as anchored (RFC 3339 with Z or offset), naive local (no offset), date-only, epoch seconds or milliseconds, zone abbreviation, ambiguous numeric date, or unparseable, and lists the hazard of each; with assumedTimeZone it also reports whether a naive time falls in a DST gap or overlap there, every instant it could mean, and offsets that contradict the zone. Bu
| Name | Type | Req | Description |
|---|---|---|---|
| assumedTimeZone | string | – | IANA zone the producer is believed to use; used for gap/overlap and offset-consistency checks. |
| timestamps | array | yes | – |
No output schema declared.
No examples provided.
number-to-words ~132
Number and cheque-amount words: English (US, UK, Indian lakh/crore) — Spells out a number or a money amount in English words for a cheque, contract or invoice, for an agent that must write the amount in words next to the figures. Locales: en-US ("one hundred twenty-three"), en-GB ("one hundred and twenty-three"), en-IN (lakh and crore, "one crore twenty lakh"). With a currency it returns the integer words, the minor-unit fraction as digits over 10^exponent ("56/100"
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
open-badges-verifier ~328
Open Badges 2.0 / 3.0 credential verifier — Verifies an Open Badges credential end to end and says what could and could not be confirmed. Accepts an Open Badges 3.0 credential (JSON with an eddsa-jcs-2022 proof, or a VC-JWT signed with EdDSA, ES256 or RS256), an Open Badges 2.0 assertion (hosted, or signed as an RS256 JWS), a hosted-assertion URL, or a baked PNG or SVG image. Checks the 2.0/3.0 required fields, the issuance and expiry windo
| Name | Type | Req | Description |
|---|---|---|---|
| credential | – | – | The credential or assertion as a JSON object (or the same as a JSON string, or a compact JWS string). |
| image | string | – | A baked badge image, base64 (data URLs accepted): a PNG with an openbadges iTXt chunk, or an SVG with an openbadges:assertion or openbadges:credential element. Up to 6 MB decoded. |
| jws | string | – | A compact JWS: an Open Badges 3.0 VC-JWT or an Open Badges 2.0 signed assertion. |
| recipientIdentity | string | – | Optional: the recipient's email or other identity to compare against the badge's recipient, including salted sha256$ and md5$ hashes. |
| url | string | – | https URL of a hosted Open Badges 2.0 assertion or a hosted 3.0 credential. |
No output schema declared.
No examples provided.
pack-size ~159
Pack sizes, MOQ, order increments, overbuy cap and price breakpoints: what to actually order — Finds the cheapest valid order quantity for a requested number of units across up to 50 supplier options, for an agent buying parts or consumables sold in packs. Each option has a pack size (units per pack or notation such as "6x100", "case of 12", "12/case", "case of 6 inners"), an optional minimum order quantity, an order increment and price breakpoints; the order is rounded up to a multiple of
| Name | Type | Req | Description |
|---|---|---|---|
| options | array | yes | – |
| overbuyCapPercent | string | – | Reject orders exceeding the request by more than this percent. |
| requested | integer | yes | Units needed. |
No output schema declared.
No examples provided.
platform-text-fit ~136
Does this text fit: SMS segments, X posts, store listings, ad and push limits — Checks up to 50 texts per call against a platform limit, for an agent writing a message, post, store listing, ad or push payload that must not be truncated or split. sms: GSM 7 bit vs UCS-2 and the exact segment boundaries per 3GPP TS 23.038 (extension characters cost 2 septets and never straddle a segment; an emoji is 2 UTF-16 units). x: weighted length per the open-source twitter-text config v3
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
pod-sufficiency ~195
Proof-of-delivery sufficiency against a required evidence list — Checks whether the proof-of-delivery evidence supplied (signature, photo, timestamp, GPS fix, recipient name, scan ...) satisfies the carrier or contract requirement list the caller gives: every required item, plus optional 'at least k of these' groups, with value bounds (for example GPS accuracy at most 30 m) and maximum age. For an agent assembling a delivery dispute or a payment release. Return
| Name | Type | Req | Description |
|---|---|---|---|
| anyOf | array | – | Alternative groups: at least atLeast (default 1) of the keys must be present. |
| asOf | string | – | Reference instant (ISO date or instant) for evidence age; required only when a need sets maxAgeDays. The check never reads the clock. |
| evidence | array | yes | Proof elements the caller holds. |
| required | array | yes | Evidence every proof must contain (key plus optional bounds). |
No output schema declared.
No examples provided.
price-change-attribution ~309
Attribute a total's change to quantity, price, FX, added and removed lines (sums exactly) — Explains why a total moved between two versions of a quote, order or invoice (up to 300 lines each), for an agent that must say how much of the change came from quantity, unit price, exchange rate, new lines and dropped lines. Lines are matched by key. Matched lines are decomposed by sequential substitution in the declared factor order (default quantity, then price, then fx), so the effects sum to
| Name | Type | Req | Description |
|---|---|---|---|
| after | array | yes | – |
| before | array | yes | – |
| currency | string | – | ISO 4217 alphabetic code, upper case. |
| exponent | integer | – | – |
| fx | object | – | Multiplier from line currency to reporting currency, before and after. Default 1 and 1. |
| order | array | – | Substitution order of the factors; each at most once. Default [quantity, price, fx]. |
| rounding | string | – | Default half-even. half-up: ties away from zero. half-down: ties toward zero. half-even: ties to the even neighbour. up: away from zero. down: toward zero. ceiling: toward +infinity. floor: toward -i… |
| statedAfterTotal | string | – | Optional stated total of `after` to verify. |
| statedBeforeTotal | string | – | Optional stated total of `before` (reporting currency) to verify. |
No output schema declared.
No examples provided.
print-estimate ~339
Print resolution, bleed and uncompressed bitmap size arithmetic — Given an image's pixel size and a print size (inches, millimetres or centimetres) plus optional bleed, margin and target ppi, returns the effective ppi over trim plus bleed, whether it meets the target, the pixel count a target ppi needs, the largest print size a target ppi allows, the safe area, and the exact uncompressed bitmap size. Built for print-on-demand, layout and image-prep agents; the t
| Name | Type | Req | Description |
|---|---|---|---|
| bitsPerChannel | integer | – | Bits per channel (default 8). |
| bleed | number | – | Bleed added on each side of the trim, in unit (default 0). |
| channels | integer | – | Channels per pixel for the raw size (default 3). |
| claimedEffectivePpi | number | – | An effective ppi you assert; checked against the computed value. |
| claimedRawBytes | integer | – | An uncompressed byte count you assert. |
| heightPx | integer | yes | Image height in pixels. |
| margin | number | – | Safe margin inside the trim on each side, in unit (default 0). |
| ppiTolerance | number | – | Accepted ppi difference for claimedEffectivePpi (default 0.5). |
| printHeight | number | – | Trim height in unit. |
| printWidth | number | – | Trim width in unit. |
| targetPpi | number | – | The resolution you require, in pixels per inch. |
| unit | string | – | Unit for print size, bleed and margin (default in). |
| widthPx | integer | yes | Image width in pixels. |
No output schema declared.
No examples provided.
pronunciation-apply ~174
Pronunciation lexicon to SSML phoneme and sub tags — Applies your pronunciation lexicon (up to 200 terms, each an IPA string or a spoken alias) to a text of up to 20000 characters and returns SSML 1.1 with <phoneme alphabet="ipa"> or <sub alias> around each whole-word match, XML-escaped, for an agent preparing text for a text-to-speech engine. Matching is whole-word, longest term first, left to right, deterministic. It does not guess pronunciations,
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | xml:lang of the speak element (default en-US). |
| lexicon | array | yes | – |
| text | string | yes | – |
| wrapSpeak | boolean | – | Wrap in <speak version="1.1"> (default true). |
No output schema declared.
No examples provided.
property-risk ~221
Property Hazard & Site Risk Report — Before an agent recommends, underwrites or screens a US property, reads free public federal hazard data for a street address or lat/lon: Census geocode, FEMA National Flood Hazard Layer flood zone, SFHA status and base flood elevation, USGS ASCE 7-22 seismic design values, FEMA National Risk Index tract ratings (wildfire, hurricane, tornado and more), OpenFEMA county disaster declarations for 10 y
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | US street address with city and state or ZIP, e.g. 1111 Lincoln Rd, Miami Beach, FL 33139. Give this or lat with lon. |
| intended_use | string | – | Optional. Reweights the score: residential counts environmental proximity 1.5x, industrial 0.5x, development counts flood and seismic 1.5x. |
| lat | number | – | Latitude in WGS84 degrees; give with lon instead of address. |
| lon | number | – | Longitude in WGS84 degrees; give with lat. |
No output schema declared.
No examples provided.
property-violations-history ~267
Property Code-Violation & Lien History (Open-Data Cities) — Before buying, leasing or insuring a US property, reads the city's own open-data code-enforcement records for one address (or a NYC BBL/BIN) and returns normalized violations with date opened, category, description, open/closed status, source severity class and record URL; deterministic counts by status, category and year; days since the latest violation; the longest repeat-citation streak (citati
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | US street address with city and state, e.g. '447 21st Ave, San Francisco, CA 94121'. Give exactly one of address, bbl or bin. |
| bbl | string | – | NYC borough-block-lot, 10 digits. |
| bin | string | – | NYC building identification number, 7 digits. |
| city | string | – | City, when not inside address. For NYC a borough name (Brooklyn, Queens, ...) narrows the match. |
| lookback_years | integer | – | Years of history to read (default 10). |
| state | string | – | Two-letter state, when not inside address. |
| zip | string | – | ZIP code (informational; not used to widen a match). |
No output schema declared.
No examples provided.
proration ~162
Proration and day-count fractions (30/360, ACT/365F, ACT/360, ACT/ACT ISDA) on half-open date ranges — Computes the year fraction of up to 100 half-open date ranges [start, end) under a named ISDA day-count convention, and optionally the prorated charge, for an agent billing a partial period or accruing interest. Conventions follow Section 4.16 of the 2006 ISDA Definitions: 30/360, 30E/360, 30E/360 (ISDA), Actual/365 (Fixed), Actual/360, Actual/Actual (ISDA), 1/1. `end` is the day immediately follo
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
qualifier-compare ~145
Requested vs quoted specification attributes: met, not met or not comparable — Compares up to 200 requested attribute requirements with the values a supplier quoted (voltage, grade, finish, tolerance, brand, certification), for an agent checking that a quote matches the request before buying. Requirements are eq, ne, gte, lte, gt, lt, between (value..max), in (a list) or present; numeric comparisons use exact decimals, an optional tolerance, and the caller's unit conversions
| Name | Type | Req | Description |
|---|---|---|---|
| caseSensitive | boolean | – | – |
| conversions | array | – | Caller-supplied unit conversions; none are built in. |
| items | array | yes | – |
No output schema declared.
No examples provided.
quote-normalize ~184
Normalise supplier quotes to one comparable unit price (currency, unit of measure, tax, discount) — Converts up to 200 quoted prices to a net price per base unit in one currency, for an agent comparing supplier quotes. Each line: price for `per` units of a unit of measure, optional tax-inclusive flag and rate, optional percentage discount, any currency. Uses only the caller's exchange rates and unit factors (1 uom = factor base units); a currency without a rate, a unit without a factor, or a tax
| Name | Type | Req | Description |
|---|---|---|---|
| baseUom | string | – | Name of the base unit prices are normalised to (default "unit"). |
| fxRates | array | – | – |
| lines | array | yes | – |
| targetCurrency | string | yes | ISO 4217 alphabetic code, upper case. |
| uomFactors | array | – | – |
No output schema declared.
No examples provided.
recipe-scale ~210
Recipe scaling with caller-declared non-linear rules — Scales up to 60 ingredient quantities by a servings ratio or a factor for an agent resizing a recipe or batch formula, applying per-ingredient rules the caller declares: linear (the labelled default), power exponent, fixed amounts, min/max clamps and rounding steps, with an optional display unit via unit-convert. Reports what rounding did (relative drift, rounds-to-zero). It does NOT know which in
| Name | Type | Req | Description |
|---|---|---|---|
| density | object | – | Default density for displayUnit conversions that cross mass and volume. |
| factor | number | – | Scale factor, instead of fromServings/toServings. |
| fromServings | number | – | Servings the recipe is written for. |
| ingredients | array | yes | Ingredients with quantity, unit and optional scaling rule. |
| maxRelativeDrift | number | – | Fail an ingredient when rounding moves it by more than this fraction (0.1 = 10%). |
| toServings | number | – | Servings wanted. |
No output schema declared.
No examples provided.
reconcile-ledger ~464
Exact Ledger Reconciler — Explains which charges, refunds and fees make up a Stripe, PayPal or bank payout, with an exact solver instead of a model: subset-sum over integer minor units (meet-in-the-middle, DP, branch-and-bound) across candidate fee schedules (percentage + fixed, tiers, caps), withholding, FX rates and rounding conventions (half-up, half-even, truncate; per line or on the total). Paste a Stripe balance or p
| Name | Type | Req | Description |
|---|---|---|---|
| conventions | object | – | Restrict the conventions searched (default: all rounding modes x both scopes x both FX date policies). |
| crossCheck | boolean | – | Run two independent LLM translations and keep only rows both produced (default true). |
| defaultCurrency | string | – | Currency for text rows that state none. |
| feeSchedules | array | – | Candidate fee schedules; the solver reports which one reconciles each settlement. Omit for no fees. |
| fxRates | array | – | Direct rates only (1 from = rate to). The latest rate dated on or before the reference date applies; an undated rate is the fallback. |
| items | array | – | Ledger lines. Amounts are signed (refunds and disputes negative) strings in major units, e.g. "1234.56". |
| limits | object | – | – |
| maxLagDays | integer | – | An item may settle at most this many days after its date. |
| nearMissToleranceMinor | integer | – | Largest residual searched when reporting the closest near-miss for an unmatched settlement. |
| settlements | array | – | Payouts or bank settlement totals to explain. |
| text | object | – | Messy source text for collections not given structurally. A CSV with a header (Stripe balance or payout-reconciliation export, PayPal activity export, bank statement) is parsed by code with no model,… |
| toleranceMinor | integer | – | Accepted |residual| per settlement in minor units (default 0 = exact). |
| withholdings | array | – | – |
No output schema declared.
No examples provided.
recurrence-expand ~435
Expand an RRULE or 5-field cron into concrete occurrences with DST handling, exclusions and conflict detection — Expands an RFC 5545 RRULE (FREQ DAILY/WEEKLY/MONTHLY/YEARLY, INTERVAL, COUNT, UNTIL, BYDAY with ordinals, BYMONTHDAY, BYMONTH, BYSETPOS, WKST; DTSTART with TZID; EXDATE) or a crontab(5) expression into up to 366 occurrences in a time zone, with the UTC instant of each, DST gap or overlap flags, caller blackout dates, a plain-English reading, and optionally the occurrences where it collides with a
| Name | Type | Req | Description |
|---|---|---|---|
| blackouts | array | – | Inclusive local date ranges to drop (holidays, freezes). |
| dtstart | string | – | Local DTSTART when the rule text has none. |
| durationMinutes | integer | – | Occurrence length, for conflict overlap. |
| exdates | array | – | Extra excluded local date-times (YYYY-MM-DDTHH:MM[:SS]) or dates (YYYY-MM-DD, excludes that day). |
| from | string | – | Local start of the output window; required for cron, default DTSTART for rrule. |
| kind | string | yes | – |
| limit | integer | – | Maximum occurrences returned (default 20). |
| other | object | – | A second rule to compare; conflicts are occurrences whose intervals overlap (equal instants when both durations are 0). |
| rule | string | yes | rrule: 'DTSTART;TZID=America/New_York:19970902T090000\nRRULE:FREQ=DAILY;COUNT=10\nEXDATE;TZID=America/New_York:19970903T090000' or just 'FREQ=...' with dtstart. cron: '*/15 9-17 * * 1-5' (dom and dow… |
| timeZone | string | – | IANA zone for local times (required for cron; for rrule unless DTSTART has TZID or Z). |
| to | string | – | Local end of the window, inclusive. |
No output schema declared.
No examples provided.
redact-text ~480
Selective PII redaction with a self-check — Redacts detected personal data at the level you choose and rescans the output with the same rules. This self-check does not prove that all personal data is gone. Pick a level: 1 government identifiers (SSN, ITIN, EIN, UK NINO, Canadian SIN, driver's license, passport), 2 adds dates of birth, 3 adds street addresses and phone numbers, 4 adds person names and email addresses. Then switch single cate
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Exact set of categories to redact; replaces the level preset when given. |
| exclude | array | – | Categories to remove from the level preset. |
| include | array | – | Categories to add to the level preset. |
| keep | array | – | Strings that must never be redacted, such as your own email address or company name. Case-insensitive, whole match. |
| level | integer | – | Cumulative preset, default 1. 1: government identifiers (SSN, ITIN, EIN, UK NINO, Canadian SIN, driver's license, passport); 2: level 1 plus dates of birth; 3: level 2 plus street addresses and phone… |
| minDigitRun | integer | – | Also redact every run of at least this many digits (spaces, dots and hyphens between digits count as part of the run). This is the number of digits, not the numeric value. |
| style | string | – | label (default): [REDACTED:SSN]. generic: [REDACTED]. numbered: [PERSON_1], same value same number. last4: [REDACTED:SSN:*6789] for numeric identifiers; this discloses the last four characters. |
| terms | array | – | Words or phrases to redact wherever they appear (business names, project names, people you already know). Case-insensitive. |
| text | string | yes | The document text to redact (plain text, Markdown, CSV, JSON or HTML source). |
| useModel | boolean | – | Add a language-model pass for names, organizations and addresses (when those categories are on). Sends the text, up to 60000 characters, to the configured model provider. Default false. |
No output schema declared.
No examples provided.
regional-economy-brief ~258
Regional Economy & Trade Brief — Given a US state, county or metro (name, FIPS or CBSA), an industry (NAICS code or description) and a role (retailer, logistics, cfo, lender, other), reads BLS LAUS and QCEW, FRED (state employment, house prices, goods exports and imports, regional CPI), Census Building Permits and USAspending live, then computes levels, year-over-year and three-year changes, location quotient, z-scores against th
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | yes | NAICS code (44-45, 722, 4841) or a plain description ("restaurants", "trucking"). |
| lookbackYears | integer | – | Years of history used for z-scores (default 5). |
| region | string | yes | A US state, county or metropolitan area by name ("Ohio", "Travis County, TX", "Phoenix metro"), state FIPS (39), county FIPS (48453) or metro CBSA code (38060). |
| regionType | string | – | Disambiguates a name that is both a county and a metro or state. |
| role | string | yes | Who the brief is for. |
No output schema declared.
No examples provided.
requirement-coverage ~167
Checklist coverage: caller requirements against caller evidence — Evaluates a checklist of requirements the caller defines (each made of needs on evidence keys: present, equals, one of, min/max, maximum age) against evidence the caller supplies, and returns met / unmet / unknown per requirement with the exact need and value that decided it. For an agent that must prove a task's acceptance criteria were covered before it reports done. Does not judge whether the p
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | – | Reference instant (ISO date or instant) for evidence age; required only when a need sets maxAgeDays. The check never reads the clock. |
| evidence | array | yes | Observed facts. Several items may share a key (conflicts surface as unknown). |
| requirements | array | yes | The checklist. |
No output schema declared.
No examples provided.
score-state ~179
Score state for tennis, golf handicap differentials and cricket overs — Replays a tennis point sequence (ITF Rules of Tennis: games, deuce, tie-breaks, match tie-break, who serves), computes a golf Score Differential and Handicap Index (World Handicap System), or tallies a cricket innings ball by ball (overs.balls, wides and no-balls, maidens, wickets), for agents that must verify a reported score. Optionally checks a claimed score against the replay and names the fir
| Name | Type | Req | Description |
|---|---|---|---|
| cricket | object | – | For sport=cricket: one innings, ball by ball. |
| golf | object | – | For sport=golf: a round, a list of differentials, or both. |
| sport | string | yes | Selects which block below is read. |
| tennis | object | – | For sport=tennis. |
No output schema declared.
No examples provided.
settlement-date ~313
Settlement date for a trade date: US equities T+1 on NYSE and Federal Reserve days, or T+n on a caller calendar — Computes the settlement date for a trade date under US equities T+1 (17 CFR 240.15c6-1, compliance date 2024-05-28) counting only days when the NYSE and the Federal Reserve Banks are open, or T+n on a named or caller calendar, and checks an asserted settlement date. The settlement-day rule (NYSE and Reserve Banks both open, so Columbus Day and Veterans Day are skipped) is our inference, not a publ
| Name | Type | Req | Description |
|---|---|---|---|
| calendar | string | – | Named holiday calendar with a source and supported date range (outside it the answer is unsupported), weekends-only (Saturday/Sunday only), or caller (only the holidays you list). |
| claimedSettlementDate | string | – | – |
| cycleDays | integer | – | custom only. |
| holidays | array | – | Extra non-business dates YYYY-MM-DD (company closures, a calendar we do not carry). |
| settlement | string | yes | us-equities: T+1 since 2024-05-28 on the us-equities-settlement calendar (2026-2028). custom: cycleDays on calendar/holidays/weekend. |
| tradeDate | string | yes | – |
| weekend | array | – | Non-business weekdays, 0=Sunday..6=Saturday. Default [0, 6]; use [5, 6] for a Friday/Saturday weekend. |
No output schema declared.
No examples provided.
shelf-life-check ~137
Is this lot still within shelf life on a given date? (unopened and after-opening limits, minimum remaining days) — For up to 100 lots, computes the expiry date from manufacture/fill date + shelf life (days, weeks, months, years; month arithmetic clamps to month end) and from opened date + after-opening life, takes the earlier, and checks it against a caller asOf date and an optional minimum remaining days at receipt; flags a labelled expiry that disagrees with the computed one. The last day of life is the expi
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | – |
| items | array | yes | – |
No output schema declared.
No examples provided.
site-access-check ~195
Site access: caller access rules against observed site facts — Checks whether an intended action on a website (read, crawl, submit, log in, ...) satisfies the access rules the caller supplies (robots rule read, terms clause, login present, rate-limit budget, captcha seen) against facts the caller observed, and says which rule blocked it or which fact is missing. For an agent deciding whether to proceed or ask. It is a reading of the caller's rules, not legal
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | The intended action, matched against each rule's appliesTo. |
| asOf | string | – | Reference instant (ISO date or instant) for evidence age; required only when a need sets maxAgeDays. The check never reads the clock. |
| evidence | array | yes | Observed site facts. |
| rules | array | yes | Access rules: needs that must hold, or with forbid:true, conditions that must not apply. |
No output schema declared.
No examples provided.
slot-intersect ~142
Common free time across participants: intersect availability windows, report who blocks — Intersects up to 20 participants' free windows (up to 200 each, half-open RFC 3339 intervals with Z or offsets, so mixed time zones are fine) into the common slots at least minMinutes long, optionally clipped to a search window; when nothing fits, names the participants whose removal would create a slot. Built for an agent scheduling a meeting from already-fetched availability. It does not read ca
| Name | Type | Req | Description |
|---|---|---|---|
| minMinutes | integer | – | Minimum slot length; default 1. |
| participants | array | yes | – |
| window | object | – | Only consider this range. |
No output schema declared.
No examples provided.
solar-position ~237
Sun position, sunrise and sunset for a place and instant (NOAA equations) — Computes sun elevation, azimuth, declination, equation of time, sunrise, solar noon and sunset (UTC) for a latitude/longitude and up to 100 caller-supplied instants using the NOAA Global Monitoring Laboratory solar calculator equations (Meeus). Polar day and polar night return sunrise and sunset as null with a reason, not an error. Reads no clock: every instant comes from the caller. Does not mode
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | ISO 8601 instant with Z or numeric offset; the call never reads the clock. |
| claim | object | – | Optional claim about the asOf instant to check; tolerances default to 0.5 deg and 2 minutes. |
| instants | array | – | Further instants, same place. |
| latitude | number | yes | Degrees north, -90 to 90. |
| longitude | number | yes | Degrees east, -180 to 180. |
| utcOffsetMinutes | integer | – | Offset from UTC used to define the local calendar day for sunrise/sunset (default 0). |
No output schema declared.
No examples provided.
speech-normalize ~162
Normalize numbers, currency, phone numbers and units for text-to-speech — Rewrites digits in up to 20000 characters of text into spoken words for a TTS engine, for locales en-US and en-GB: cardinals, ordinals, years (with a preceding cue such as "in" or a month) and decades, decimals, percentages, currency with ISO 4217 minor units ("$12.50" -> "twelve dollars and fifty cents"), phone numbers read digit by digit, and SI/common units with locale spelling (meter/metre). O
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | BCP 47 tag. en-US (default) and en-GB are supported; anything else returns unsupported. |
| text | string | yes | – |
No output schema declared.
No examples provided.
storage-charge-clock ~397
Storage, demurrage or detention charge: free-time end date, chargeable days and tiered amount — Counts days between a received date and a released date for storage, demurrage, detention or parking charges: you state whether the receipt day and the release day count, how free days are counted (calendar or business days on a named or caller calendar), and a tiered per-day rate schedule by chargeable day number; returns the last free day, chargeable days, a per-tier breakdown and the total in m
| Name | Type | Req | Description |
|---|---|---|---|
| calendar | string | – | Named holiday calendar with a source and supported date range (outside it the answer is unsupported), weekends-only (Saturday/Sunday only), or caller (only the holidays you list). |
| chargeCounting | string | yes | Whether chargeable days skip weekends/holidays. |
| claimedChargeMinor | integer | – | – |
| currency | string | yes | ISO 4217 code in capitals, e.g. USD. rateMinor is in this currency's minor units (cents for USD). |
| freeCounting | string | yes | Whether free days skip weekends/holidays; business needs calendar. |
| freeDays | integer | yes | Free days before charges start; 0 for none. |
| holidays | array | – | Extra non-business dates YYYY-MM-DD (company closures, a calendar we do not carry). |
| receiptDayCounts | boolean | yes | Whether the day of receipt is day 1. |
| receivedOn | string | yes | Date the goods or container were received, YYYY-MM-DD. |
| releaseDayCounts | boolean | yes | Whether the release day is counted. |
| releasedOn | string | yes | Date released, YYYY-MM-DD; not before receivedOn. |
| tiers | array | yes | – |
| weekend | array | – | Non-business weekdays, 0=Sunday..6=Saturday. Default [0, 6]; use [5, 6] for a Friday/Saturday weekend. |
No output schema declared.
No examples provided.
subtitle-lint ~246
Subtitle lint: SRT and WebVTT overlaps, duration, reading speed, line length — Parses an SRT or WebVTT file (up to 400000 characters, 4000 cues) and checks every cue for an agent about to deliver or burn in captions: end after start, overlaps and out-of-order cues, minimum gap, minimum and maximum duration, lines per cue, characters per line and characters per second (markup tags are not counted). Rules come from a named profile (netflix-en-adult, netflix-en-children, values
| Name | Type | Req | Description |
|---|---|---|---|
| custom | object | – | Your own rules; these override profile values. |
| format | string | – | Default: vtt if the text starts with WEBVTT, else srt. |
| frameRate | number | – | Needed to turn a minimum gap in frames into milliseconds. |
| profile | string | – | netflix-en-adult: 42 chars/line, 2 lines, 20 cps, 5/6 s to 7 s, 2-frame gap. netflix-en-children: same at 17 cps. |
| text | string | yes | The whole .srt or .vtt file. |
No output schema declared.
No examples provided.
syllable-count ~157
Syllable counts per line, caller dictionary first, labelled English heuristic second — Counts syllables per word and per line for English text, using your dictionary entries first and otherwise a rule-based estimator (vowel groups, silent e, -ed/-es, consonant+le). Optionally checks each line against a target pattern such as 5-7-5. Where the rules cannot decide (vowel pairs like ia/io/eo, acronyms, numerals, non-Latin scripts) the word is a range or abstains, and a line whose count
| Name | Type | Req | Description |
|---|---|---|---|
| dictionary | array | – | Caller counts; they override the rules. |
| lines | array | yes | – |
| pattern | array | – | Same length as lines. |
No output schema declared.
No examples provided.
tariff-engineer ~230
Global Customs & Tariff Engineering Optimizer — Classifies a product under the HTS with GRI reasoning and verifies the code and general (MFN) rate against the live USITC schedule, flags when a specific sibling subheading may outrank the chosen residual one, separates lower-duty options from reclassification risk with dollar exposure, lists lawful physical tariff-engineering changes, and drafts an accurate commercial invoice description. Leads w
| Name | Type | Req | Description |
|---|---|---|---|
| currentHtsCode | string | – | – |
| customsValueUsd | number | – | Entered value, used to estimate duty and savings. |
| destinationCountry | string | yes | – |
| importStateOfAssembly | string | – | – |
| intendedUse | string | yes | – |
| materialsBreakdown | array | yes | – |
| originCountry | string | yes | – |
| productDescription | string | – | Construction, dimensions, how it works, packaging. |
| productName | string | yes | – |
| productUrl | string | – | Public product or spec-sheet page. Its text is read to supplement productDescription; if it cannot be read the request still succeeds and says so in warnings. |
No output schema declared.
No examples provided.
tax-id-format ~120
VAT / tax-id format and check digit (AT, BE, DE, DK, FI) — Checks the structure and check digit of up to 100 EU VAT numbers per call (Austria, Belgium, Germany, Denmark, Finland), for an agent about to put a supplier or customer VAT number on an invoice or into a record. Every other country answers unsupported rather than guessing a pattern. It never says whether the number is registered or active (that needs VIES or the national register), and a pass is
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
temporal-constraints ~158
Are these timing constraints satisfiable? Earliest/latest time per event, or the conflicting constraints — Solves a simple temporal network: up to 40 named time points, up to 200 difference constraints 'b is between min and max minutes after a' and optional fixed instants, relative to a caller origin instant. When consistent it returns each point's earliest and latest feasible instant (where bounded); when not, it returns the cycle of constraints that contradict each other, with the total impossible sl
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | array | yes | – |
| fixed | array | – | – |
| origin | string | yes | Instant that point 'origin' (an implicit extra point) is at; all minutes are relative to it. |
| points | array | yes | – |
No output schema declared.
No examples provided.
time-bucket-check ~193
DST hazards for hourly and daily buckets in a zone: skipped hours, repeated hours, 23- and 25-hour days — For a time zone and a date range of up to 1100 days, lists every offset transition and what it does to local bucketing: the hourly labels that never occur (spring-forward), the hourly labels that occur twice and would merge two real hours when grouped by local time (fall-back), and the 23-, 24.5- or 25-hour days; optionally checks up to 500 caller hourly labels (YYYY-MM-DDTHH:00) for non-existent
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | First local date, inclusive. |
| labels | array | – | Local hour labels to check, e.g. 2026-03-08T02:00. |
| timeZone | string | yes | – |
| to | string | yes | Last local date, inclusive. |
No output schema declared.
No examples provided.
timecode-convert ~203
SMPTE timecode conversion: drop-frame and non-drop, frames, exact seconds — Converts up to 200 timecodes, frame counts or times between SMPTE HH:MM:SS:FF (non-drop), HH:MM:SS;FF (drop-frame, 29.97 and 59.94), frame numbers and exact rational seconds, for an agent editing video, captions or logs at a stated frame rate. Rates are integers, a rational like 30000/1001, or the named 23.976, 29.97, 59.94, 119.88; any other decimal is rejected, never rounded. Integer arithmetic
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| rate | string | yes | 24, 25, 30, 50, 60, 24000/1001, or the names 23.976, 29.97, 59.94, 119.88. |
No output schema declared.
No examples provided.
tolerance-stack ~231
One-dimensional tolerance stack-up (worst-case and RSS) — Computes the minimum and maximum of a linear dimensional stack (the gap) from signed contributions with symmetric, unequal-bilateral, unilateral or min/max limits, both by exact worst-case arithmetic and by root-sum-square, names the dominant contributor and tests the gap against a required minimum and/or maximum. For mechanical designers and agents checking clearances. It does not do 2D or 3D sta
| Name | Type | Req | Description |
|---|---|---|---|
| dimensions | array | yes | At most 100. Give nominal with tol, or nominal with plus and/or minus (unilateral: one of them), or min and max. |
| method | string | – | Which result decides status against the requirement (default worst-case). Both are always reported. |
| reportSigma | number | – | RSS: report the gap at this many sigma (default equals sigmaLevel). |
| requirement | object | – | Allowed gap range. |
| sigmaLevel | number | – | RSS: each tolerance is this many sigma (default 3). |
| unit | string | – | Label for the single unit all numbers share (not converted). |
No output schema declared.
No examples provided.
transcribe-url ~208
Transcribe an audio or video file URL (Whisper, timestamps, SRT, VTT) — Transcribes a public audio or video FILE URL (podcast enclosure, meeting recording, voice memo; mp3, wav, mp4/m4a, ogg, webm, flac; up to 25 MB and 30 minutes) with Whisper large-v3-turbo on Cloudflare Workers AI. Returns timestamped segments plus SRT and VTT subtitles and the plain text, bound to the media's SHA-256. Does NOT accept YouTube, Spotify or any streaming page (the URL must be the medi
| Name | Type | Req | Description |
|---|---|---|---|
| formats | array | – | Outputs to include; default all. |
| language | string | – | ISO 639-1 language code of the speech (for example en); detected when omitted. |
| max_minutes | integer | – | Reject audio longer than this, default 30. |
| url | string | yes | https URL of the audio or video file itself. |
No output schema declared.
No examples provided.
unit-convert ~151
Exact unit conversion with dimensional analysis (NIST SP 811) — Converts up to 100 values between units for an agent that needs the exact factor and a refusal when the units do not match: SI and NIST SP 811 length, mass, time, volume, pressure, energy, power, temperature, with compound expressions like kg*m/s^2. Rejects incompatible dimensions, converts absolute temperatures affinely through kelvin and temperature differences linearly, and converts mass to vol
| Name | Type | Req | Description |
|---|---|---|---|
| density | object | – | Default density for items that cross mass and volume. |
| items | array | yes | Conversions to run. |
| precision | integer | – | Significant digits of the reported value. Default 12. |
No output schema declared.
No examples provided.
vin-decode ~128
VIN decode: manufacturer (WMI), model year, check digit — Decodes up to 50 VINs per call for an agent handling a vehicle listing, claim or order: validates the 17 characters and letters I/O/Q, the position-9 check digit (49 CFR 565.15), the world manufacturer identifier from a bundled NHTSA vPIC snapshot, and the model year from position 10. Position 10 repeats every 30 years: pass vehicleClass light (position 7 resolves the century) or asOf, otherwise b
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
week-number ~217
Week number and week-year for dates under ISO 8601, US or custom rules (53-week years) — Returns the week number, week-year, number of weeks in that year and the week's first and last day for up to 200 dates under ISO 8601 (Monday start, week 1 holds 4 January), the US convention (Sunday start, week 1 holds 1 January) or a custom weekStart/minimalDays rule, and checks an asserted week or week-year (2027-01-01 is ISO 2026-W53). Built for an agent reading or writing week-based dates in
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| minimalDays | integer | – | Days of the new year the first week must contain (custom). |
| system | string | yes | iso: weekStart Monday, minimalDays 4. us: weekStart Sunday, minimalDays 1. custom: give weekStart and minimalDays. |
| weekStart | integer | – | 0=Sunday..6=Saturday (custom). |
No output schema declared.
No examples provided.
x509-inspect ~239
X.509 certificate inspection from PEM — Takes a PEM-encoded X.509 certificate and returns its fields (subject, issuer, serial, validity window, SANs, key usage, EKU, basic constraints, signature algorithm, public key algorithm and bit size) plus a fail-on-issue audit: expired or not-yet-valid, hostname/SAN mismatch per RFC 6125 §6.4.3 wildcards, weak signature (SHA-1), short RSA (<2048), serverAuth without SAN (CABF BR 7.1.4.2.1). Decod
| Name | Type | Req | Description |
|---|---|---|---|
| hostname | string | – | Optional hostname to check against the certificate's SANs. |
| intermediates | array | – | Intermediate certs (PEM) between leaf and anchor. |
| maxChainDepth | integer | – | Chain depth cap (default 8). |
| nowIso | string | – | Override 'now' for deterministic tests. |
| pem | string | yes | A PEM block beginning with '-----BEGIN CERTIFICATE-----'. |
| trustAnchors | array | – | Trust anchors (PEM). When present, chain cryptographic verification runs. |
No output schema declared.
No examples provided.
How do I install the WritersLogic business agents MCP server?
WritersLogic business agents is a hosted endpoint at https://agents.writerslogic.com/mcp/business, 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-business 'https://agents.writerslogic.com/mcp/business'
What is the WritersLogic business agents MCP server?
WritersLogic business agents is an MCP server listed in the public MCP registry as com.writerslogic.agents/writerslogic-business. Medical-bill audit, chargeback, contract terminator, lead enrichment, filing integrity. This page covers its hosted endpoint (https://agents.writerslogic.com/mcp/business).
Is the WritersLogic business agents MCP server safe to use?
WritersLogic business agents scores 63 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 business agents MCP server expose?
WritersLogic business agents exposes 95 tools: lead-enrichment, competitor-battlecard, medical-bill-auditor, chargeback-fighter, contract-terminator, and 90 more. Their descriptions and schemas cost roughly 21,458 tokens of context every time the server is loaded.
Does the WritersLogic business agents MCP server require authentication?
No. We connected to WritersLogic business agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the WritersLogic business agents MCP server still maintained?
WritersLogic business 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 business agents MCP server?
VerifyMCP ran 12 checks on WritersLogic business 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 business 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.