store.pureservices/crm-csv-preflight
Registry code: a8459d7627824965
Sales List Rescue by Pure Services. Pass a contact/lead CSV as text to preflight_csv to get a preflight report before a CRM import. Limits: 500 data rows and 64 KiB of CSV per call. This checker only detects issues. It changes nothing in your data and returns no cleaned file. The checks are pattern-based; they don't verify mailbox deliverability. Nothing you send is stored or logged.
- endpoint
- https://pureservices.store/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is store.pureservices/crm-csv-preflight live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is store.pureservices/crm-csv-preflight free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does store.pureservices/crm-csv-preflight have?
- 2 tools: preflight_csv, preflight_sample.
- Is store.pureservices/crm-csv-preflight safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 2 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
preflight_sample open 1h ago
Runs the same checks as preflight_csv on the checker's built-in sample CSV (fake placeholder data) and returns the sample plus its report, so you can see the report format without sending a file. Detection only; does not store or log your CSV.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linespreflight_csv unknown 1h ago
Checks a contact or lead CSV (passed as text, up to 500 data rows and 64 KiB) before a CRM import and reports what it finds: duplicate emails (matched ignoring case and surrounding spaces), invalid email syntax, role or shared inboxes (info@, sales@ and similar), blank required fields (placeholders like N/A, null and - count as blank), phone numbers not written as + country code and digits only (with a suggested form when the fix is mechanical), country and state spelling drift, mixed or ambiguous date formats, and file problems (garbled characters, ragged rows, formula-like cells, stray spaces, header issues). Detection only: it changes nothing, returns no cleaned file, and does not store or log your CSV. Pattern-based; it does not check that mailboxes exist. Same checks as the free Sales List Rescue CSV preflight checker on pureservices.store.
{ "type": "object", "required": [ "csv" ], "properties": { "csv": { "type": "string", "description": "The full CSV text including the header row. Comma, semicolon, tab or pipe delimited (auto-detected)." }, "email_column": { "type": "string", "description": "Header name of the email column. Optional; auto-detected when omitted." }, "phone_column": { "type": "string", "description": "Header name of the phone column. Optional; auto-detected when omitted." }, "required_columns": { "type": "array", "items": { "type": "string" }, "description": "Header names that must not be blank. Optional; defaults to the detected email, first name, last name and company columns." }, "default_country_code": { "enum": [ "1", "44", "61", "49", "33", "91", "" ], "type": "string", "default": "1", "description": "Calling code assumed for phone numbers without a + prefix: 1 (US/Canada), 44, 61, 49, 33, 91, or \"\" for no default." } }, "additionalProperties": false }arguments 42 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ida8459d7627824965.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/a8459d7627824965/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/a8459d7627824965?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.