-
Notifications
You must be signed in to change notification settings - Fork 0
Add agent-readiness discovery metadata #4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,36 @@ | ||
| { | ||
| "name": "getbased", | ||
| "description": "MCP server that exposes your getbased health data — blood work context, biomarker sections, and an optional RAG knowledge base — as tools for any MCP-compatible agent. Your data stays on your device; the server reads a read-only context summary, not raw records.", | ||
| "version": "0.2.0", | ||
| "transport": "stdio", | ||
| "hosting": "local", | ||
| "homepage": "https://getbased.health", | ||
| "documentation": "https://app.getbased.health/docs/guide/agent-access", | ||
| "repository": "https://github.com/elkimek/getbased-agents/tree/main/packages/mcp", | ||
| "license": "GPL-3.0-only", | ||
| "install": { | ||
| "pypi": "getbased-mcp", | ||
| "command": "getbased-mcp", | ||
| "bundle": { | ||
| "package": "getbased-agent-stack", | ||
| "repository": "https://github.com/elkimek/getbased-agents/tree/main/packages/stack", | ||
| "description": "Meta-package that bundles the MCP server with the RAG backend and example Claude Code / Hermes / OpenClaw configs." | ||
| } | ||
| }, | ||
| "authentication": { | ||
| "type": "token", | ||
| "env": "GETBASED_TOKEN", | ||
| "description": "Read-only token generated in the getbased app under Settings > Data > Messenger Access. Grants access to lab-context text only — no raw data, no write access. Revocable at any time by regenerating the token." | ||
| }, | ||
| "gateway": "https://sync.getbased.health", | ||
| "tools": [ | ||
| { "name": "getbased_lab_context", "description": "Full lab summary — biomarkers, ranges, trends, context cards, supplements, goals. Pass a profile to target a specific profile." }, | ||
| { "name": "getbased_section", "description": "Get a specific section (e.g. hormones, lipids) or list all available sections. Token-efficient alternative to the full dump." }, | ||
| { "name": "getbased_list_profiles", "description": "List available profiles by name and ID." }, | ||
| { "name": "knowledge_search", "description": "Semantic search across the active library of your RAG knowledge base. Requires the getbased-rag server; degrades gracefully if unavailable." }, | ||
| { "name": "knowledge_list_libraries", "description": "List all knowledge-base libraries and show which is active." }, | ||
| { "name": "knowledge_activate_library", "description": "Switch the active knowledge-base library for subsequent searches." }, | ||
| { "name": "knowledge_stats", "description": "Per-source chunk counts for the active library — useful for diagnosing missing results." }, | ||
| { "name": "getbased_lens_config", "description": "Show the Custom Knowledge Source endpoint configuration used by the getbased app." } | ||
| ] | ||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Content-Signalis placed inside theUser-agent: *record (between the agent directive and theAllow/Disallowlines). Standard robots.txt parsers ignore unknown directives in a record, so crawlers are unaffected. However, if Cloudflare'sContent-Signalparser treats this as a per-agent field rather than a global one, the signal may be scoped only to the wildcard agent block rather than applying site-wide. Consider moving it above the firstUser-agent:line or placing it after all records to make the global intent explicit and future-proof the parsing.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Leaving this as-is. Per Cloudflare's Content Signals spec,
Content-Signalis a per-record directive — it belongs inside aUser-agentgroup alongsideAllow/Disallow, not above the firstUser-agent:line. Placing it in theUser-agent: *record is the documented pattern and applies site-wide via the wildcard. The specific bot records below (OAI-SearchBot, etc.) don't inherit it, but since every signal isyesand those bots are already fully allowed, repeating it there would just be noise.The vercel.json comment is addressed in 89fb86d (relative URLs).