Watchlist tracking
Reviewed for relevance and future tracking value.
MCP100 Assessment
Watchlist / Tracking
Why we’re tracking it
Follow Go SDK and protocol-version support as tRPC Agent evolves
Reviewed · Documentation review; complete setup workflow not independently tested
Best fit
Go teams building production agent systems with tools, memory, MCP and multi-agent workflows.
What we know
A Go-native agent framework with LLM agents, graphs, multi-agent collaboration, tools, MCP, memory, retrieval, evaluation and observability.
Maintenance / activity evidence
- Observed (UTC)codeexecutor/jupyter: delete a started kernel when websocket dialing …
Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.
Verification gaps / watch-outs
- Installation and comprehensive security have not been independently audited.
- Application grants tools/memory/code execution. Writes: Depends on configured tools/code execution.
- Application/provider-defined
- Sensitive access: Prompts, Memory, Artifacts, Code
- A broad agent framework can be given powerful tools and code execution; deployment configuration determines effective risk.
Full authority, access and evidence limits are available in Review context and Access & risk.
Popularity
1,846 repository stars
Stars observed Oct 6, 2026.
All limitations / Review context
Which MCP client and tool patterns does the current Go framework support?
The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.
- A broad agent framework can be given powerful tools and code execution; deployment configuration determines effective risk.
- Application grants tools/memory/code execution.
- Application/provider-defined
- Can persist sessions, memory, artifacts and telemetry depending on setup.
- Reviewed write actions: Depends on configured tools/code execution
- Sensitive access: Prompts, Memory, Artifacts, Code
- Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
- A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
- No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
- The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
- Authentication, tool permissions, code execution and storage are application-defined.
Original activity observations
- 2026-09-25T11:03:48Z: codeexecutor/jupyter: delete a started kernel when websocket dialing …
Technical identity
github.com/trpc-group/trpc-agent-go- Exact implementation source
- https://github.com/trpc-group/trpc-agent-go ↗
- Reviewed resource type
- Framework
- Repository identity
- trpc-group/trpc-agent-go
Evidence & Sources
- Evidence basis
- Recorded source evidence
- Setup runtime verification
- Not independently runtime-tested by MCP100 for this setup workflow.
Reviewed · Latest source observation
- GitHub repository ↗
trpc-group/trpc-agent-go
Recorded repository material and project history.
- Evidence source ↗
trpc-group.github.io/trpc-agent-go/
Source material retained for this review.
Includes references whose attribution is not established.
Setup · Watchlist
Framework setup
Publisher instructions.
Source evidence observed .
Additional setup details required — see the specific gaps below.
Install / connect
Publisher instructionstRPC-Agent-Go is a Go agent-development framework, not a standalone MCP server.
publisher setup entry · Publisher instructions
git clone https://github.com/trpc-group/trpc-agent-go.gitConfigure / authenticate
MCP100 setup guideRequires Go 1.21+. Configure LLM provider key and run the official examples/runner demo. MCP integration depends on agent implementation.
Check connection
Suggested checkRun go test on own project or help/demo in isolated environment; no MCP server auto-registration.
Remove / uninstall / revoke
MCP100 setup guideRemove the Go module from the application's go.mod through its package/import changes and `go mod tidy`; stop any server built using the framework. `trpc-agent-go` is a Go framework, not a standalone MCP process to unregister.
Client unregistration, program uninstall, persistent-data deletion, and credential revocation must be treated separately.
Application dependency cleanup · MCP100 composed guide
go mod tidy
What it does
A Go-native agent framework with LLM agents, graphs, multi-agent collaboration, tools, MCP, memory, retrieval, evaluation and observability.
- Capability
- AI & Reasoning
- Resource type
- Framework
- Industry
- Software & Technology
- Best fit
- Go teams building production agent systems with tools, memory, MCP and multi-agent workflows.
Representative uses
- Build multi-agent workflows
- Integrate function tools/MCP/search/code execution
- Persist sessions and memory
- Evaluate and observe agents
Limitations
- Authentication, tool permissions, code execution and storage are application-defined.
Reviewed access
Access & risk
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
- Authentication
- Application/provider-defined
- Permissions
- Application grants tools/memory/code execution.
- Data handling
- Can persist sessions, memory, artifacts and telemetry depending on setup.
- Cost
- unknown
- Risk and cautions
- A broad agent framework can be given powerful tools and code execution; deployment configuration determines effective risk.
Access scope and cautions
- Write actions
- Depends on configured tools/code execution
- Sensitive access
- Prompts Memory Artifacts Code
- Risk level
- high
FAQ
Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.
Which tasks are documented for this implementation?
What authentication is documented?
Can it modify data or perform write operations?
What data-handling boundary should I consider?
What limitations and risks should I check before use?
Is this an official MCP?
tRPC Group is listed as First-party MCP in MCP100’s current evidence.