API Tools
bsn.expert
Provides BSN account lookup and tag management tools, enabling retrieval of account details and exploration of relationship tags.
ENDPOINT 1
https://bsn.expert/mcp
MCP server metadata
- Name
- bsn-expert
- Version
- 0.1.0
Read public BSN Expert snapshot data. Use bsn.account.get for a general public account lookup; its compact known-tag summary points to bsn.account.tags when linked accounts, unknown tags, or reciprocal-pair details are needed. Use bsn.account.tags directly for questions specifically about an account's tags or relationships, and bsn.tags.list to understand the tag catalog and reciprocal-pair semantics. This server never signs transactions and does not prove account ownership.
Known tools 3
bsn.account.tagsUse when the question is specifically about an account's tags or relationships.
Inferred read-onlybsn.tags.listReturn the BSN relationship-tag catalog with localized descriptions, categories, single-value rules, pair type, reciprocal tag, and strong-pair requirement.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.bsn-expert]
url = "https://bsn.expert/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"bsn-expert": {
"type": "http",
"url": "https://bsn.expert/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: bsn-expert
Remote MCP URL: https://bsn.expert/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"bsn-expert": {
"url": "https://bsn.expert/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"bsn-expert": {
"type": "http",
"url": "https://bsn.expert/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "bsn-expert",
"transport": "streamable-http",
"url": "https://bsn.expert/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.