SOLVED — buy work already done
REMOTE · API.TROVEFIELD.AI · SCANNED AUG 8
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 →
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 Usability63
- 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 Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.trovefield.ai
claude mcp add --transport http ai-trovefield-solved 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": {
"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.
- 8 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
- 7 Aug 26 59
First indexed and scored.
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 8 Aug 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 |
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 |
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.
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.