
Execute crypto-tax-loss-harvester-mcp
io.github.EvozimPublished by GitHub account Evozimv2.0.0Updated Oct 24, 2026
Premium agentic endpoint for crypto-tax-loss-harvester-mcp.
Overview
A remote MCP endpoint for a crypto tax-loss harvester, reached over SSE and paid per call with a signed USDC payment header.
- What you can do
- Connects an assistant to a hosted crypto tax-loss harvesting service over SSE at a fixed remote endpoint. No tools are listed in the manifest, so the specific operations are not documented here. Access is metered: each request is settled through an x402 V2 payment on Base Mainnet in USDC, authorized by a signed header. The registry describes it only as a premium agentic endpoint.
- When to use it
- Consider it only if you want an assistant to reach a hosted crypto tax-loss harvesting service and are prepared to pay per request in USDC on Base Mainnet. Because no tools or documentation are provided, confirm what it actually does before relying on it.
- Requirements
- A remote SSE endpoint at the provider's host; nothing is installed locally. A wallet able to produce an EIP-3009 TransferWithAuthorization signature, supplied in the Payment-Signature header, and enough USDC on Base Mainnet to cover the stated per-request charge. Network access to the endpoint.
Installation
In SourceWeft
- Open Execute crypto-tax-loss-harvester-mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via SSE. 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.Evozim%2Fcrypto-tax-loss-harvester-mcp/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": {
"execute-crypto-tax-loss-harvester": {
"type": "sse",
"url": "https://api.m2mcent.com/crypto-tax-loss-harvester-mcp/sse"
}
}
}Tools
0Version history
1- v2.0.0LatestSep 16, 2026
Score
67% 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.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.