
TrustLayer
io.github.goatgauchoPublished by GitHub account goatgauchov1.0.0Updated Oct 25, 2026
Agent reputation scoring: trust scores, Sybil detection, cross-chain identity for 133K+ agents
Overview
TrustLayer is a remote MCP endpoint that gives an assistant agent reputation data: trust scores, Sybil detection and cross-chain identity for a large set of AI/
- What you can do
- Provides agent reputation scoring, including trust scores for agents, Sybil detection, and cross-chain identity lookups. The manifest lists no individual tools, so the exact operations available to an assistant are not documented here. It is a hosted remote endpoint, so an assistant connects to it rather than running anything locally.
- When to use it
- Worth considering when an assistant needs to judge whether an AI agent or counterparty is trustworthy, screen for Sybil or fake identities, or resolve an agent's identity across chains. Less useful if you only need general web data or local tooling.
- Requirements
- A remote MCP client that supports streamable HTTP, connecting to the provider's hosted endpoint. The manifest declares no authentication, environment variables or headers, and no local runtime or package is needed.
Installation
In SourceWeft
- Open TrustLayer in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.goatgaucho%2Ftrustlayer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"trustlayer": {
"type": "http",
"url": "https://api.thetrustlayer.xyz/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
60% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.