Burs-IA Tools
MCP server · bursia-tools-production.up.railway.app · found in a public list · checked since 2026-10-30
Live, handshake completed · latest check
Audits websites for AI-agent readiness, plus DNS, TLS and header checks and utilities.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means
Placed in Check whether AI agents can read a site: Check robots.txt, llms.txt, structured data and agent files that decide whether AI crawlers and agents can use a site.
https://bursia-tools-production.up.railway.app/mcp MCP endpoint (Streamable HTTP)The name is the registry's label, not ours. Not reviewed by a person.
Our checks
An unpaid request daily, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hourssince 2026-10-30 | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-30 | 1 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-30 | 1 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Tools listed by the server
bursia_agent_readinessbursia_base64bursia_case_convertbursia_check_agent_cardbursia_check_agents_jsonbursia_check_llms_txtbursia_check_mcp_discoverybursia_check_openapibursia_check_robotsbursia_check_sitemapbursia_check_skillsbursia_check_x402bursia_cidr_infobursia_color_convertbursia_contrast_ratiobursia_cron_explainbursia_csv_to_jsonbursia_date_diffbursia_dns_recordsbursia_email_syntaxbursia_hashbursia_hmacbursia_html_escapebursia_iban_validatebursia_ip_classifybursia_json_diffbursia_json_formatbursia_json_pathbursia_json_to_csvbursia_json_validatebursia_jwt_decodebursia_levenshteinbursia_luhn_checkbursia_mcp_registry_searchbursia_password_generatebursia_security_headersbursia_semver_comparebursia_slugifybursia_text_statsbursia_timestamp_convert+6
- Tools
- 46
- This list since
- 2026-10-30
- First listed to us
- 2026-10-30
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Interface it declares
- Protocol
- MCP 2025-06-18
- Capabilities
- tools
- Transports
- streamable-http
As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions
What it says about itself
- For
- agentsfrom its listing's description, read 2026-10-30
From the service's own text, put in short words by a small AI model and shown only where its own words support it (stated-facts/5): its claims, not checked by us. Anything not listed, it does not state. Definitions
Calls it declares
bursia_agent_readiness url*bursia_check_agent_card url*bursia_check_llms_txt url*bursia_check_mcp_discovery url*bursia_check_openapi url*bursia_check_robots url*bursia_check_agents_json url*bursia_check_skills url*bursia_check_x402 url*bursia_check_sitemap url*bursia_json_validate text*bursia_jwt_decode token*
From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Listing
In the capability tree: Web access and automation / Website analysis / Check whether AI agents can read a site (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-30. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Live, handshake completed HTTP 200 | 289 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
- Limited evidence: monitored for 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_06e0aaccef783692