Repository navigation
feat(wallet-mcp): add Tereno plugin - #27
Open
RobMartello wants to merge 1 commit into
Open
RobMartello wants to merge 1 commit into
RobMartello wants to merge 1 commit into
Conversation
🟡 Heimdall Review Status
|
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Adds
skills/wallet-mcp/plugins/tereno.md(integration: http-api,chains: [base]): pre-action onchain verification and shared-cache lookups on Base that an agent can run before a Wallet MCPswaporsend_calls:token.launch.guard— simulated buy/sell exit viaeth_call, DEX liquidity reserve depth, LP lock/burn status, and owner privileges.token.holders.guard— top-10 holder concentration, ETH funding-origin graph, and deployer-funded holder clusters.contract.guard— runtime bytecode presence, EIP-1967 proxy implementation slots, pause state, and static selector flags.token.metadata— ERC-20name,symbol,decimals, and block-freshtotalSupply.chain.snapshot— latest Base block, timestamp, base fee, and suggested gas parameters.GET /api/v1/capabilities/price) and content-addressed artifact verification (GET /api/v1/evidence/{artifactId}).The plugin is strictly read-only: it never constructs or returns transaction calldata. Paid checks settle in Base USDC (
eip155:8453, x402 v2) through Wallet MCP'sinitiate_x402_request→ approval flow →complete_x402_request.Scope — adds only
skills/wallet-mcp/plugins/tereno.mdand reuses existing tag vocabulary (ai-agents,agent-commerce,token-launches,trading,dex).SKILL.mdand the maintainer-managed conformance/examples tables are untouched perreferences/plugin-spec.md#contribution-scope.Change type
Validation
Validated frontmatter, canonical section headings, and section order against
skills/wallet-mcp/references/plugin-spec.md.Verified live endpoints (
GET https://www.tereno.xyz/api/v1/capabilities/price,402x402 v2 challenge on/api/v1/capabilities/*/invoke, andhttps://www.tereno.xyz/openapi.json).Ran
python3 -m unittest discover -s tests(38 passed) andpython3 scripts/build-distributions.py dist.Confirmed
git diff --checkand verified SSH commit signature.Generated portable manifest and MCP config validate against the vendored Agent Plugins schemas
Package paths and skill references remain inside each generated plugin root
Marketplace, skills, MCP, and icon paths are valid
Exactly one canonical skill library; generated copies are not committed
Claude compatibility metadata/endpoint and marketplace sources agree with the portable package
Tool schemas, authorization, and retry behavior reviewed
README and changelog updated; versions consistent (not modified per Wallet MCP plugin Contribution Scope)
No unapproved disclosures or sensitive data
Signed commits
Base / Wallet MCP Plugin Submission Agreement
By checking the box below, I agree and represent on behalf of the protocol/entity it references that:
I am authorized to submit this plugin on behalf of the protocol/entity it references;
the plugin does not infringe or misappropriate any third party's rights;
the plugin and the underlying protocol comply with all applicable laws, and my API enforces the same geofencing and eligibility restrictions as my own user-facing app;
the plugin is in full compliance with our protocol's/entity's then-current terms and conditions, and if not, submission and use thereafter is considered a formal written exemption to such terms and conditions;
the plugin accurately describes its behavior and contains no hidden, deceptive, or malicious instructions, and my API will not return malicious or unexpected calldata;
the protocol/entity is solely responsible for the plugin, and submitting a plugin is subject to the applicable terms of service as using a "Service"; and
Base may modify, decline to list, or remove the plugin at any time, for any reason.
I have read and agree to the Base MCP Plugin Submission Agreement above.
Release considerations
Third-party Wallet MCP plugin addition only (
skills/wallet-mcp/plugins/tereno.md).requires.allowlist: [www.tereno.xyz]is declared forweb_requestprovisioning upon maintainer acceptance.