# Agent Tools MCP

- Registry name: `io.github.why-see/agent-tools-mcp` · version 1.1.0
- Categories (automatic, keyword rules): Payments & accounting, Finance & markets, Datasets & public data, Search & data, Utilities
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.why-see%2Fagent-tools-mcp
- Server page: https://mcpstation.net/s/io.github.why-see--agent-tools-mcp.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://agent-tools-mcp.yvan11.workers.dev/mcp`

## Tools (as reported by the server, not verified)

- `is-card-safe`: 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.
- `is-email-safe`: 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.
- `is-iban-safe`: 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.
- `is-iso-date-safe`: 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.
- `is-ip-safe`: 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.
- `is-json-safe`: 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.
- `is-password-safe`: 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.
- `is-phone-e164`: 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.
- `is-uuid-safe`: 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.
- `is-url-safe`: 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.
- `is-us-tin-safe`: 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.
- `is-vat-safe`: 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.
- `optimize-dataset`: 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.
- `optimize-google-tag`: 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.
- `minify-html`: 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.
- `minify-js`: 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.
- `minify-css`: Reduce whitespace in CSS snippets. Use for basic stylesheet cleanup rather than production minification. Not a full CSS parser; visually test the result.
- `minify-prompt`: 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.
- `strip-ansi`: Strip terminal ANSI escape codes from text. Use to make colorized logs readable for indexing or display. Returns plain text without interpreting log entries.
- `generate-avatar`: Create an SVG placeholder profile icon. Use for synthetic avatars in demos and UI prototypes. Returns SVG markup, not a photorealistic likeness.
- `generate-card-number`: 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.
- `generate-color`: 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.
- `generate-dataset`: 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.
- `generate-fake-data`: 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.
- `generate-hash`: 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.
- `generate-lorem`: Generate lorem ipsum placeholder copy. Use for mock layouts needing filler words, sentences or paragraphs. Returns synthetic copy, not sourced editorial content.
- `generate-password`: 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.
- `generate-phone-number`: 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.
- `generate-prompt`: 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.
- `generate-slug`: Convert a title into a Unicode-aware URL slug. Use when forming new path segments from headings. Inspect output before publishing permanent URLs.
- `generate-ssn`: 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.
- `generate-token`: Generate token strings or UUIDs. Use for test identifiers; use generate-password for password fixtures. Seeded output is predictable and unsuitable for authentication credentials.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html