Home / MCP registry index / io.github.soyeladice-svg/bursia-tools

Burs-IA Tools

io.github.soyeladice-svg/bursia-tools in the official MCP registry. Endpoint https://bursia-tools-production.up.railway.app/mcp.

The registry describes it as: Free read-only tools for agents: agent-readiness audit, TLS/DNS/header checks, MCP search, utils.

We read its 47 tools on 2026-11-01. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http bursia-tools https://bursia-tools-production.up.railway.app/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "bursia-tools": {
      "url": "https://bursia-tools-production.up.railway.app/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"bursia-tools","type":"http","url":"https://bursia-tools-production.up.railway.app/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

bursia_agent_readiness bursia_compare_readiness bursia_check_agent_card bursia_check_llms_txt bursia_check_mcp_discovery bursia_check_openapi bursia_check_robots bursia_check_agents_json bursia_check_skills bursia_check_x402 bursia_check_sitemap bursia_json_validate bursia_jwt_decode bursia_hash bursia_base64 bursia_url_parse bursia_uuid bursia_timestamp_convert bursia_cron_explain bursia_text_stats bursia_slugify bursia_json_format bursia_json_diff bursia_json_path bursia_csv_to_json bursia_json_to_csv bursia_url_encode bursia_html_escape bursia_case_convert bursia_semver_compare bursia_ip_classify bursia_cidr_info bursia_email_syntax bursia_luhn_check bursia_iban_validate bursia_color_convert bursia_contrast_ratio bursia_unit_convert bursia_date_diff bursia_timezone_convert bursia_password_generate bursia_levenshtein bursia_hmac bursia_security_headers bursia_dns_records bursia_tls_certificate bursia_mcp_registry_search

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-01): 9e84a2707454de9c. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-soyeladice-svg-bursia-tools/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-soyeladice-svg-bursia-tools)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.