Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BSP_API_URLNoOverride BSP API base URL (default: https://api.biologicalsovereigntyprotocol.com).
BSP_NETWORKNoNetwork to use: mainnet or testnet (default: mainnet).
BSP_BEO_DOMAINYesThe user's BSP identity domain (e.g. alice.bsp). Required.
BSP_IEO_API_KEYNoAPI key for IEO-scoped operations (bsp_list_beos, bsp_list_ieos, bsp_submit_biorecord).
BSP_PRIVATE_KEYNoHex-encoded Ed25519 private key required for write tools (bsp_lock_beo, bsp_unlock_beo, bsp_destroy_beo, bsp_revoke_all_tokens).
BSP_REGISTRY_URLNoOverride relayer/registry endpoint (default: https://api.biologicalsovereigntyprotocol.com).
BSP_CONSENT_TOKEN_IDNoToken ID issued by the BEO holder. Required for data access tools.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
bsp_get_biorecordsA

Read BioRecords from the user's BEO (biological identity). Requires an active ConsentToken with READ_RECORDS intent. Returns biological measurements in BSP format with values, units, reference ranges, and collection timestamps.

bsp_get_beo_summaryA

Get a structured overview of the user's biological profile — what categories of data exist, how many records per category, most recent measurement dates, and overall data completeness. Requires active session consent. Use this before bsp_get_biorecords to understand data scope.

bsp_resolve_biomarkerA

Look up information about a specific BSP biomarker code — name, category, level, and clinical context. Public taxonomy data — no consent required.

bsp_list_categoriesA

List all BSP taxonomy categories with level information. Public data — no consent required. Use this to understand what biological data categories exist and which are relevant for a user's health question.

bsp_lock_beoA

Emergency lock — freezes the BEO immediately. No reads or writes permitted while locked. Only the BEO holder can lock or unlock. Requires the private key configured in BSP_PRIVATE_KEY.

bsp_unlock_beoA

Unlock a previously locked BEO. Requires the BEO holder's private key.

bsp_destroy_beoA

IRREVERSIBLE — Permanently destroy a BEO (LGPD Art. 18 / GDPR Art. 17). Nullifies public key, revokes all ConsentTokens, releases domain. The user MUST confirm before executing this tool.

bsp_revoke_all_tokensA

Emergency revocation — revokes ALL active ConsentTokens for a BEO. No institution will be able to access any data after this.

bsp_check_consentA

Check the current consent configuration — which BEO is connected, which data categories and intents are authorized, and when the token expires. Run this first to understand what data you are allowed to access in this session.

bsp_list_beosB

List BEOs accessible to the configured IEO

bsp_list_ieosB

List registered IEOs on the BSP network

bsp_verify_consentB

Verify if a ConsentToken is valid and has the required intent

bsp_submit_biorecordA

Submit a BioRecord for a BEO (requires SUBMIT_RECORD consent)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Biological-Sovereignty-Protocol/bsp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server