Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Agent Tools MCP

REMOTE · AGENT-TOOLS-MCP.YVAN11.WORKERS.DEV

32 free MCP tools for data validation, text optimization, and synthetic test data.

+4 this week 72 Trust /100

Last scanned (54 minutes ago)

Scores higher than 58% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 2765 tokens (~86/item across 32 items; 32 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management38
  • Stability check failed: schema churn in the 18 days we've observed: 7 tool removals, 0 breaking changes, 0 auth/transport breaks, 7 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
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; "minify-html" implies "remove" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 32 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 34 to 38.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 28 to 31.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 21 to 24.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 14 to 18.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 4 to 8.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 1.

  • 20 Oct 26 −3
    • Stability: 0.03 → fail ▼ security
    • A breaking change shipped without a version bump: still 1.1.0 ▼ security
    • Tool “is-dataset-minify” was removed ▼ security
    • Tool “is-google-tag” was removed ▼ security
    • Tool “is-html-minify” was removed ▼ security
    • Tool “is-minify-css” was removed ▼ security
    • Tool “is-minify-js” was removed ▼ security
    • Tool “is-prompt-minify” was removed ▼ security
    • Tool “is-strip-ansi” was removed ▼ security
    • Tool “is-ip-safe” rewrote its description, which is the text the model reads security
    • Tool “generate-avatar” rewrote its description, which is the text the model reads security
    • Tool “generate-card-number” rewrote its description, which is the text the model reads security
    • Tool “generate-color” rewrote its description, which is the text the model reads security
    • Tool “generate-dataset” rewrote its description, which is the text the model reads security
    • Tool “generate-fake-data” rewrote its description, which is the text the model reads security
    • Tool “generate-hash” rewrote its description, which is the text the model reads security
    • Tool “generate-lorem” rewrote its description, which is the text the model reads security
    • Tool “generate-password” rewrote its description, which is the text the model reads security
    • Tool “generate-phone-number” rewrote its description, which is the text the model reads security
    • Tool “generate-prompt” rewrote its description, which is the text the model reads security
    • Tool “generate-slug” rewrote its description, which is the text the model reads security
    • Tool “generate-ssn” rewrote its description, which is the text the model reads security
    • Tool “generate-token” rewrote its description, which is the text the model reads security
    • Tool “is-card-safe” rewrote its description, which is the text the model reads security
    • Tool “is-email-safe” rewrote its description, which is the text the model reads security
    • Tool “is-iban-safe” rewrote its description, which is the text the model reads security
    • Tool “is-iso-date-safe” rewrote its description, which is the text the model reads security
    • Tool “is-json-safe” rewrote its description, which is the text the model reads security
    • Tool “is-password-safe” rewrote its description, which is the text the model reads security
    • Tool “is-phone-e164” rewrote its description, which is the text the model reads security
    • Tool “is-url-safe” rewrote its description, which is the text the model reads security
    • Tool “is-us-tin-safe” rewrote its description, which is the text the model reads security
    • Tool “is-uuid-safe” rewrote its description, which is the text the model reads security
    • Tool “is-vat-safe” rewrote its description, which is the text the model reads security
    • Schema quality: 102 → 86 ▲ functional
    • Destructive annotations: pass → 0 functional
    • New tool “minify-css” functional
    • New tool “minify-html” functional
    • New tool “minify-js” functional
    • New tool “minify-prompt” functional
    • New tool “optimize-dataset” functional
    • New tool “optimize-google-tag” functional
    • New tool “strip-ansi” functional
    • “generate-phone-number” reworded the description of “city” cosmetic
    • “generate-prompt” reworded the description of “seed” cosmetic
    • “generate-prompt” reworded the description of “template” cosmetic
    • “generate-prompt” reworded the description of “vars” cosmetic
    • Tool “generate-card-number” changed its title: Generate a synthetic card test number → Generate a synthetic payment card fixture cosmetic
    • Tool “is-phone-e164” changed its title: Normalize an international phone number → Validate E.164 phone number syntax cosmetic
  • 19 Oct 26 +1
    • Tool “is-dataset-minify” rewrote its description, which is the text the model reads security
    • Tool “is-google-tag” rewrote its description, which is the text the model reads security
    • Tool “is-html-minify” rewrote its description, which is the text the model reads security
    • Tool “is-minify-css” rewrote its description, which is the text the model reads security
    • Tool “is-minify-js” rewrote its description, which is the text the model reads security
    • Tool “is-prompt-minify” rewrote its description, which is the text the model reads security
    • Tool “is-strip-ansi” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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 5 Nov 2026 · Probed https://agent-tools-mcp.yvan11.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=yvan11.workers.dev CN=WE1,O=Google Trust Services,C=US 1 Oct 2026 30 Dec 2026 ECDSA 256 ECDSA-SHA256 a8e0397d2a9f44f813498397adf4ed46
SANs: yvan11.workers.dev, *.yvan11.workers.dev
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 insecure

Validation of agent-tools-mcp.yvan11.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agent-tools-mcp.yvan11.workers.dev/mcp Verified 200
http (plaintext) http://agent-tools-mcp.yvan11.workers.dev/mcp Inconclusive 405
MCP tools · 32 exposed · ~2,765 tokens

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 →

Tool Tokens
generate-avatar ~112

Create an SVG placeholder profile icon. Use for synthetic avatars in demos and UI prototypes. Returns SVG markup, not a photorealistic likeness.

NameTypeReqDescription
patternstring–Avatar layout: initials, blocks, circles or random.
seedstring–Optional deterministic seed for repeatable test fixtures; do not use as a secret.
sizeinteger–SVG width and height in pixels, from 32 to 256.
textstring–Optional initials or label used to customize the placeholder.

No output schema declared.

No examples provided.

generate-card-number ~84

Generate a synthetic payment-card fixture. Use for payment-form UI tests requiring a Luhn-valid card number. Returns {number, brand, expiry, cvc}; values are synthetic, not issued credentials.

NameTypeReqDescription
brandstring–Synthetic card brand: visa, mastercard, amex or discover.
seedstring–Optional deterministic seed for reproducible fake card fixtures.

No output schema declared.

No examples provided.

generate-color ~151

Generate a palette from a base color and harmony scheme. Use for design prototypes; defaults: random base, triadic scheme, five hex colors. Returns {base, scheme, colors, textOnBase}; text color is heuristic, not a WCAG contrast check.

NameTypeReqDescription
basestring–Optional base color such as #3366ff.
countinteger–Number of colors, from 1 to 12.
formatstring–Output color notation: hex, rgb or hsl.
schemestring–Palette harmony algorithm: complementary, triadic, tetradic, analogous, monochrome or random.
seedstring–Optional deterministic seed for repeatable palette generation.

No output schema declared.

No examples provided.

generate-dataset ~122

Generate synthetic rows as JSON, JSONL or CSV. Use for data import/export tests; use generate-fake-data for preset people or company fixtures. Returns at most eight records without accessing a database.

NameTypeReqDescription
countinteger–Number of records to generate, 1–8, default 3.
formatstring–Output format: json, jsonl or csv.
schemaobject–Optional map of field names to upstream synthetic field specifications; no real records.
seedstring–Optional deterministic seed for reproducible test rows.

No output schema declared.

No examples provided.

generate-fake-data ~92

Create fictional users, companies, addresses or rows. Use to seed demos with preset records; use generate-dataset for custom fields. Synthetic values are not verified identities.

NameTypeReqDescription
countinteger–Requested number of synthetic records, up to eight.
kindstringyesFixture category: user, company, address or rows.
seedstring–Optional deterministic seed to reproduce the same fake records.

No output schema declared.

No examples provided.

generate-hash ~88

Compute SHA-256 or legacy MD5 text digests. Use for non-secret content fingerprints; generate-token creates new IDs instead. Returns a hex digest; unsuitable for password storage or key derivation.

NameTypeReqDescription
algostring–Digest algorithm: sha-256 (default) or legacy md5.
textstringyesPublic or synthetic text to digest; never send secrets for hashing.

No output schema declared.

No examples provided.

generate-lorem ~87

Generate lorem ipsum placeholder copy. Use for mock layouts needing filler words, sentences or paragraphs. Returns synthetic copy, not sourced editorial content.

NameTypeReqDescription
countinteger–Number of units, from 1 to 8; default 3.
seedstring–Optional deterministic seed for reproducible placeholder text.
unitsstring–Output unit: words, sentences or paragraphs.

No output schema declared.

No examples provided.

generate-password ~92

Generate random or seeded test passwords. Use for demo login fields; use generate-token for identifiers. Seeded values are predictable and visible to MCP clients; not a secure credential vault.

NameTypeReqDescription
lengthinteger–Desired password length, 8–256 characters.
seedstring–Optional deterministic seed for testing only; seeded output is predictable.
symbolsboolean–Whether punctuation/symbol characters are included.

No output schema declared.

No examples provided.

generate-phone-number ~134

Generate fictional US-format phone numbers. Use for US demo phone fields; when supplied, city selects a local area-code pool and must match state. Returns an array of fictional (AAA) 555-01XX numbers; no subscriber lookup.

NameTypeReqDescription
citystring–Optional city: Los Angeles, San Francisco, New York, Houston or Miami; must match state if given.
countinteger–Number of fabricated numbers, up to eight.
seedstring–Optional deterministic seed for repeatable test numbers.
statestring–Optional US state abbreviation: CA, NY, TX or FL.

No output schema declared.

No examples provided.

generate-prompt ~140

Fill a prompt template with supplied variables. Use {name} placeholders with matching vars.name; missing variables become empty text. Returns a prompt string without invoking a model; code/image modes can add framing.

NameTypeReqDescription
seedstring–Optional deterministic seed for the {{RAND_INT:min,max}} helper, not ordinary placeholders.
templatestringyesTemplate text, e.g. Hello {name}; omitted variables are replaced with empty text.
typestring–Prompt template category: text, code or image; default text.
varsobject–Object mapping placeholder names to values, e.g. {"name":"Ada"} for {name}.

No output schema declared.

No examples provided.

generate-slug ~74

Convert a title into a Unicode-aware URL slug. Use when forming new path segments from headings. Inspect output before publishing permanent URLs.

NameTypeReqDescription
maxLengthinteger–Maximum slug length, 1–160 characters; omit for the upstream default.
textstringyesSource title to normalize, such as Café startups!.

No output schema declared.

No examples provided.

generate-ssn ~128

Generate fictional US SSN-style test identifiers. Use for SSN test fields; use generate-fake-data for mixed-record fixtures. Returns a string for count=1, otherwise an array; structural validity does not confirm issuance.

NameTypeReqDescription
countinteger–Number of synthetic SSN-style fixtures, 1–8.
formattedboolean–Whether to add standard dashes to the generated identifier.
seedstring–Optional deterministic seed for repeatable fake identifiers.
validboolean–Whether fixtures should pass the generator's structural validity rules, not actual issuance checks.

No output schema declared.

No examples provided.

generate-token ~97

Generate token strings or UUIDs. Use for test identifiers; use generate-password for password fixtures. Seeded output is predictable and unsuitable for authentication credentials.

NameTypeReqDescription
lengthinteger–Output length parameter, 1–256, where applicable to the selected token type.
seedstring–Optional deterministic seed, intended for reproducible test output only.
typestringyesToken format: uuid, hex, base64 or numeric.

No output schema declared.

No examples provided.

is-card-safe ~72

Check payment-card brand, length and Luhn checksum. Use with synthetic card numbers in payment-form tests. Returns {ok, normalized?, brand?, last4?, issues}; not a payment authorization or fraud check.

NameTypeReqDescription
numberstringyesSynthetic payment-card number string to examine; do not provide real card details.

No output schema declared.

No examples provided.

is-email-safe ~63

Check conservative ASCII email address syntax. Use to reject malformed addresses in forms and test fixtures. Returns true or false; does not check mailbox existence or deliverability.

NameTypeReqDescription
emailstringyesEmail address string to check, such as founder@example.com; ASCII format only.

No output schema declared.

No examples provided.

is-iban-safe ~77

Check IBAN country rules, length and checksum against a bundled registry. Use to screen public or synthetic IBANs in test data. Returns {ok, normalized?, issues}; does not verify account ownership or transferability.

NameTypeReqDescription
ibanstringyesIBAN string, optionally with spaces; do not submit real private bank account details.

No output schema declared.

No examples provided.

is-ip-safe ~85

Check IPv4 or IPv6 literal-address syntax. Use to screen candidate IP strings, not test reachability or geolocation. Returns {ok, version, issues}; version is 4, 6 or null.

NameTypeReqDescription
ipstringyesIPv4 or IPv6 literal address such as 192.0.2.1 or 2001:db8::1.

No output schema declared.

No examples provided.

is-iso-date-safe ~69

Check Gregorian YYYY-MM-DD calendar dates, including leap days. Use for date-only form fields, not timestamps or timezone offsets. Returns true for a valid date, otherwise false.

NameTypeReqDescription
datestringyesCandidate date formatted YYYY-MM-DD, such as 2024-02-29.

No output schema declared.

No examples provided.

is-json-safe ~88

Parse JSON with bounded depth, key counts and input size. Use to screen JSON without execution; use optimize-dataset for JSONL or CSV cleanup. Returns {ok, issues, bytes, depth, keys, value?}; parsed value is included only when valid.

NameTypeReqDescription
jsonstringyesJSON document as a string, up to 4096 characters; depth and key counts are limited.

No output schema declared.

No examples provided.

is-password-safe ~70

Evaluate password strength using local heuristics. Use only with dummy passwords when testing password policies. Returns {ok, score, entropyBits, length, sets, reasons, suggestions}; no breach-database lookup.

NameTypeReqDescription
passwordstringyesFictitious test password; never supply an actual password or secret.

No output schema declared.

No examples provided.

is-phone-e164 ~73

Check phone number syntax against E.164 after local normalization. Use to test international number formats, including spaces or 00 prefixes. Returns true or false, not the normalized number; no subscriber or reachability check.

NameTypeReqDescription
phonestringyesCandidate internationally formatted telephone number, for example +66812345678.

No output schema declared.

No examples provided.

is-url-safe ~63

Check absolute HTTP or HTTPS URL syntax. Use to screen links before display or storage. Returns true or false; does not visit or assess the site's safety.

NameTypeReqDescription
urlstringyesAbsolute HTTP(S) URL string; other schemes such as javascript: are not supported.

No output schema declared.

No examples provided.

is-us-tin-safe ~73

Check synthetic US EIN, SSN or ITIN number formats. Use with tax-ID input fixtures, never real personal identifiers. Returns {ok, normalized?, type, issues}; does not verify IRS issuance or identity.

NameTypeReqDescription
tinstringyesSynthetic US taxpayer identifier string; do not submit actual personal identifiers.

No output schema declared.

No examples provided.

is-uuid-safe ~85

Check canonical UUID syntax and optional RFC variant/version. Use to validate UUIDs; use generate-token to create them. Returns true or false; does not check uniqueness or resource existence.

NameTypeReqDescription
uuidstringyesUUID string in canonical hyphenated format.
versioninteger–Optional UUID version number from 1 to 8; omit to accept any supported version.

No output schema declared.

No examples provided.

is-vat-safe ~64

Check country-specific VAT number patterns. Use to screen VAT fixtures before form submission. Returns {ok, country?, normalized?, issues}; no VIES lookup or active-registration check.

NameTypeReqDescription
vatstringyesCountry-prefixed VAT number string such as DE123456789.

No output schema declared.

No examples provided.

minify-css ~55

Reduce whitespace in CSS snippets. Use for basic stylesheet cleanup rather than production minification. Not a full CSS parser; visually test the result.

NameTypeReqDescription
codestringyesCSS source code string, limited to 4096 characters.

No output schema declared.

No examples provided.

minify-html ~70

Remove comments and compact whitespace in HTML fragments. Use for small, controlled HTML snippets, not full document compilation. Returns an HTML string; preserves pre, textarea, script and style contents. Regression-test rendered output.

NameTypeReqDescription
htmlstringyesOriginal HTML source as text, up to 4096 characters.

No output schema declared.

No examples provided.

minify-js ~63

Compact small JavaScript snippets. Use for basic source cleanup, not AST-aware production minification. Returns JavaScript text, sometimes unchanged for complex syntax; regression-test its behavior.

NameTypeReqDescription
codestringyesJavaScript source code string, limited to 4096 characters.

No output schema declared.

No examples provided.

minify-prompt ~64

Normalize prompt whitespace and line breaks. Use to compact formatting before calling a model; filler phrases are not removed. Returns trimmed text with normalized spacing; review prompts where whitespace carries meaning.

NameTypeReqDescription
textstringyesPrompt text to compact, up to 4096 characters.

No output schema declared.

No examples provided.

optimize-dataset ~95

Clean and compact JSON, JSONL or CSV rows. Use for small datasets; use is-json-safe to check JSON syntax without changes. Returns text in the selected format; trims strings, deduplicates rows and may drop mostly empty columns.

NameTypeReqDescription
formatstring–Parsing format: auto detects, or explicitly select json, jsonl or csv.
inputstringyesSource dataset text (maximum 4096 characters).

No output schema declared.

No examples provided.

optimize-google-tag ~83

Rebuild GA4 gtag.js markup from a G- measurement ID. Use on existing GA4 snippets, not GTM containers or consent setup. Returns replacement HTML with async loading and a config call, or original input if no G- ID exists. Review lost settings and consent.

NameTypeReqDescription
htmlstringyesExisting HTML snippet containing the Google Analytics tag to optimize.

No output schema declared.

No examples provided.

strip-ansi ~52

Strip terminal ANSI escape codes from text. Use to make colorized logs readable for indexing or display. Returns plain text without interpreting log entries.

NameTypeReqDescription
textstringyesTerminal output string containing optional ANSI escape sequences.

No output schema declared.

No examples provided.

Install

How do I install the Agent Tools MCP server?

Agent Tools MCP is a hosted endpoint at https://agent-tools-mcp.yvan11.workers.dev/mcp, 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 · agent-tools-mcp.yvan11.workers.dev

# add to Claude Code
claude mcp add --transport http why-see-agent-tools-mcp 'https://agent-tools-mcp.yvan11.workers.dev/mcp'
Common questions

What is the Agent Tools MCP server?

Agent Tools MCP is listed in the public MCP registry as io.github.why-see/agent-tools-mcp. 32 free MCP tools for data validation, text optimization, and synthetic test data. This page covers its hosted endpoint (https://agent-tools-mcp.yvan11.workers.dev/mcp).

Is the Agent Tools MCP server safe to use?

Agent Tools MCP scores 72 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 Agent Tools MCP server expose?

Agent Tools MCP exposes 32 tools: is-card-safe, is-email-safe, is-iban-safe, is-iso-date-safe, is-ip-safe, and 27 more. Their descriptions and schemas cost roughly 2,765 tokens of context every time the server is loaded.

Does the Agent Tools MCP server require authentication?

No. We connected to Agent Tools MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Agent Tools MCP server still maintained?

Agent Tools MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.