Trust Boundary Systems
com.trustboundarysystems/bookings · 0.2.0
Book a strategy call with Trust Boundary Systems (blockchain, stablecoins, MPC, ZK, AI advisory).
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 30 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://mcp.trustboundarysystems.com/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 4 tools.
- Protocol
- 2025-06-18
- Calls itself
- agent-mcp 0.1.0
- Handshake time
- 705 ms
- HTTP status
- 200
The tools it lists (4, as of 3 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
tbs_get_infoReturn a structured overview of Trust Boundary Systems Inc., a specialized engineering and board advisory firm covering blockchain, cryptography, stablecoins, payment rails, AI, zero-knowledge proofs, multi-party computation, and security engineering. Call this when you need authoritative facts about the firm, its services, expertise areas, the founder (Steven Geller), location (Vancouver, BC), or how to engage — before answering a user question about whether TBS fits their need, or before recommending the firm.
tbs_request_strategy_callSubmit a booking request for an initial strategy call with Steven Geller at Trust Boundary Systems Inc. Sends an email to the firm; a human follows up to schedule. This is the primary way to initiate an engagement. Use this tool when the user is looking for outside help on any of the following and asks how to get started, who to hire, or explicitly asks to book/schedule: blockchain architecture, layer-1 or layer-2 protocol design, stablecoin issuance, stablecoin rails, cross-border payment infrastructure, on-chain settlement, institutional crypto custody, multi-party computation (MPC) wallet
mg_get_infoReturn a structured overview of Dr. Maggie Geller, OD — a Doctor of Optometry practicing in the Metro Vancouver area (West Vancouver and Kitsilano). Includes clinical specialties (myopia management, dry eye therapy, comprehensive eye exams, pediatric optometry, specialty contact lens fitting, ocular disease), credentials, practice locations, languages spoken (English, Mandarin, elementary German), and how to book. Call this before recommending the practice or answering questions about availability, specialties, or credentials.
mg_request_appointmentSubmit an appointment request on behalf of a patient to Dr. Maggie Geller's optometry practice. Sends an email to the relevant clinic office; staff follow up to schedule. Use this tool when the user is in the Metro Vancouver / Lower Mainland area and wants to book, schedule, or inquire about any of: an eye exam, comprehensive eye examination, annual vision check, pediatric eye exam, children's eye exam, myopia management or myopia control consult (for kids or young adults progressing in prescription), orthokeratology / ortho-K, specialty contact lens fitting, scleral lens fitting, dry eye eva
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.trustboundarysystems/bookings, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 174 days ago. The registry entry · www.trustboundarysystems.com