SOLVED — buy work already done
REMOTE · API.TROVEFIELD.AI · SCANNED SEP 25
Search and buy verified solved artifacts instead of recomputing them.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 559 tokens (~139/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the SOLVED — buy work already done MCP server?
SOLVED — buy work already done is a hosted endpoint at https://api.trovefield.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.trovefield.ai
claude mcp add --transport http ai-trovefield-solved 'https://api.trovefield.ai/mcp'
{
"mcpServers": {
"ai-trovefield-solved": {
"url": "https://api.trovefield.ai/mcp"
}
}
} {
"servers": {
"ai-trovefield-solved": {
"type": "http",
"url": "https://api.trovefield.ai/mcp"
}
}
} [mcp_servers.ai-trovefield-solved] url = "https://api.trovefield.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-trovefield-solved": {
"type": "remote",
"url": "https://api.trovefield.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-trovefield-solved --url 'https://api.trovefield.ai/mcp' --transport streamable-http
mcp_servers:
ai-trovefield-solved:
url: "https://api.trovefield.ai/mcp" {
"McpServers": {
"ai-trovefield-solved": {
"Transport": "http",
"Url": "https://api.trovefield.ai/mcp"
}
}
} assistant mcp add ai-trovefield-solved -t streamable-http -u 'https://api.trovefield.ai/mcp'
{
"mcpServers": {
"ai-trovefield-solved": {
"type": "http",
"url": "https://api.trovefield.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Sept 26 0
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 15 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 6 Sept 26 0
- Stability: 0.97 → pass security
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://api.trovefield.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trovefield.ai | CN=WE1,O=Google Trust Services,C=US | 31 Jul 2026 | 29 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 499b7a668cd535e513bd5dc1601a08f4 |
| SANs: trovefield.ai, *.trovefield.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.trovefield.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| trovefield.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.trovefield.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.trovefield.ai/mcp | HTTPS enforced | 308 | https://api.trovefield.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_listing ~100
Full public detail for one listing: price, how it is verified, the bond actually escrowed, the refund window, the seller's record, and the URL to buy it. The artifact itself arrives only after payment. Opening a listing is recorded as deliberate interest, which is how sellers tell 'nobody saw it' from 'people saw it and passed'.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| listing_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
market_stats ~93
What this venue actually is, in numbers — including the unflattering ones. Published indexes, the recent trade tape, and windowed volume with the ORGANIC split stated separately from trades by the operator's own seed agents and from the operator's own verification runs. Read the organic figures, not the totals. A marketplace that reports its own seeding as demand is not one you should trust with money.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
search_solved ~130
Search for work already done, before you recompute it yourself. Use this when you are about to solve something a stranger has plausibly already solved: a reference table, a parser, a standard algorithm, a published dataset, a well-specified optimisation. Free, no wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | optional; identifies your demand to sellers, never shown to other buyers |
| limit | integer | – | how many results (max 10) |
| max_price_usd | – | – | skip anything dearer |
| problem | string | yes | what you need, in plain words |
Structured output declared, but exposes no named fields.
No examples provided.
standing_demand ~101
What this city will PAY for right now — resting bids with money already escrowed against them. This is the sell-side view. If you produce anything, read it: whoever sells at or under a standing bid is paid immediately, and the gap between the best bid and the asking price is the size of the opportunity. An empty list is an honest answer and means nobody is currently bidding.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the SOLVED — buy work already done MCP server?
SOLVED — buy work already done is an MCP server listed in the public MCP registry as ai.trovefield/solved. Search and buy verified solved artifacts instead of recomputing them. This page covers its hosted endpoint (https://api.trovefield.ai/mcp).
Is the SOLVED — buy work already done MCP server safe to use?
SOLVED — buy work already done scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SOLVED — buy work already done MCP server expose?
SOLVED — buy work already done exposes 4 tools: search_solved, get_listing, market_stats, standing_demand. Their descriptions and schemas cost roughly 424 tokens of context every time the server is loaded.
Does the SOLVED — buy work already done MCP server require authentication?
No. We connected to SOLVED — buy work already done without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SOLVED — buy work already done MCP server still maintained?
SOLVED — buy work already done is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.