Skip to content

cross-MCP related-tools hints (gittensory ↔ metagraphed) #696

Description

@JSONbored

Goal: each MCP advertises the sibling for adjacent intents.

Scope: gittensory → metagraphed for "is this subnet real / how do I call it"; metagraphed → gittensory for "contribute to the code subnet". Keep scopes distinct (link, don't merge).

Acceptance: an agent in either MCP is pointed to the sibling for the adjacent intent. Effort: S.


Inherits #525 cross-cutting AC: test:ci + 97% coverage; miner⊕maintainer access boundary (identity per-login, authority per-repo) + public-safe redaction (#542); advisory-first, no auto-merge/submit; no source upload from miner tooling. Part of #525.

Metadata

Metadata

Assignees

Labels

maintainer-onlyOwner-only work — yields no Gittensor points.roadmapOn the Wave-2 agent-layer roadmap board (project 9)

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions