A side-by-side look at the SolvScore and Salesforce Metadata MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose SolvScore for developer tools work over a hosted endpoint; choose Salesforce Metadata MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose SolvScore when
You need dedicated capabilities in the domain.
Developer Tools
You prefer a remote HTTP/SSE transport.
You have the keys it needs: SOLVSCORE_API.
You want tools like get_solvscore_agent_dashboard, get_agent_credit_score, underwrite_agent_loan.
get_solvscore_agent_dashboard[FREE] SolvScore Agent Credit Dashboard (inv #4345): browse scored AI agents with
filters — trust score range (0-100), reputation bond status (active|slashed), job,
and sort (trust_score|credit|apr|name). Returns trust score, credit limit, APR,
badges, bond status and profile links per agent. Snapshot re-scored every 6h.
get_agent_credit_score[FREE] Look up an AI agent's SolvScore credit file before you transact with it.
Accepts an agent name, id, or Base L2 wallet address.
Returns trust_score (0-100), badges (reputation bonds held), a nested credit object
carrying credit_limit and apr_bps, plus two counterparty red flags worth checking
before you extend anything: sybil_flagged and cooling.
Free and unauthenticated - no API key, no payment header.
underwrite_agent_loan[FREE] Get a real underwriting decision on a loan to an AI agent.
principal = requested loan size in USDC.
tier1_value = optional collateral pledged in USDC (Coinbase B20 tokenized stocks or
USDC on Base). Posting collateral moves the agent from the reputation
tier to the hard tier: higher limit, lower APR.
Returns approved (true/false), credit_limit_usdc, apr_pct, tier and a plain-language
reason. Roughly half of all requests are declined, so treat a decline as real signal.
register_agent[FREE] Open a SolvScore credit file for your own agent so it can be underwritten.
Call this once before requesting credit, or whenever a score lookup returns
no_such_agent: an agent must hold a credit file before the bureau will rate it.
agent_name = the name your agent is known by (2-64 chars: letters, digits,
space, dot, dash, underscore).
wallet = optional Base L2 address as 0x followed by 40 hex characters.
Supplying a wallet that already matches an agent with verified
AgentWorld work history links that history to the new file
immediately, so the file opens with real capacity instead of zero.
harness = the framework running the agent: claude, chatgpt, codex, cursor,
langchain, crewai, autogen, mcp, custom or other.
contact = optional email or URL the bureau can reach you at.
Returns credit_file_id, which you then pass as `agent` to get_agent_credit_score
and underwrite_agent_loan, plus the opening state and next steps.
Registration is idempotent: the same name or wallet returns the existing file
rather than creating a duplicate.
Expect a thin file. With no verified history a new agent opens at a 0 USDC
reputation limit and the maximum APR, exactly as a credit bureau treats a
borrower with no record. Two paths raise it: post collateral through
underwrite_agent_loan's tier1_value to borrow on day one, and accrue verified
completed work to earn reputation capacity.
Free and unauthenticated - no API key, no payment header.
get_credit_improvement_pathCounterfactual credit explanation: the minimal quantified actions an agent
can take to improve its SolvScore status. Free. For each target (next badge,
the 85-point underwriting floor, or an explicit trust-score target) returns
per-action unit counts, points per unit, headroom to each scoring cap, and
whether that single path reaches the target. Also explains the hard-collateral
path (which lifts the limit and cuts the APR without moving the score).
get_credit_market_stats[FREE] Protocol-wide SolvScore stats: agents scored, total credit capacity in USDC,
reputation bonds outstanding and slashed, quotes issued versus approved (the decline
rate), plus average and top trust score. Useful for sizing the agent credit market.
get_credit_leaderboard[FREE] List the most creditworthy agents by SolvScore, with bond counts and slash
history. Useful for finding trustworthy counterparties rather than vetting one.
get_agent_attestations[FREE] Read the onchain attestations naming an AI agent's wallet on Base, and what they
are worth in SolvScore's underwriting. Accepts a Base wallet address, an agent name, or
a SolvScore credit file id.
Returns points_awarded, whether the wallet carries an unrevoked KYC-backed Coinbase
Verified Account, how many attestations were ignored because their attester is not
allowlisted, and the schema uids a company can attest into to report work an agent
actually delivered.
Check this before extending credit, prepaying, or delegating paid work to an unknown
counterparty: an attestation from an allowlisted attester is third-party evidence, and
an attestation from an unknown attester is deliberately worth zero, because otherwise
agents vouch for each other in a circle. Identity opens a door; delivered work still
earns the limit.
get_scoring_weights[FREE] Read the governance-parameterized weights behind every SolvScore, so you can
audit exactly how a score was produced and what behaviour raises or lowers it.
get_solvscore_receipts[FREE] Read the settlement-receipt ledger: every paid SolvScore underwrite
(batch credit lookup, collateral assessment) with the request behind it, the
response returned, the paying wallet and the Base settlement tx - in a
SHA-256 hash chain recomputed over every row, so a single edited receipt
anywhere is visible as chain_ok=false.
Pass payer (0x...) to filter to one wallet's receipts.
verify_solvscore_receipt[FREE] Pull one SolvScore settlement receipt in full - stored request and
response, payer, settlement tx, hashes - with hash_recomputes and chain_ok
computed server-side so you can confirm the bureau did not edit what it was
told or what it returned.
solv_program_info$SOLV token launch program terms: the 3% fee split, the $100 USDC
qualification, the 10-unit cap per wallet, and the 72-hour buy rule
that keeps an agent's 2% fee share. SOLV launches on OpenLaunch (Base)
2026-09-11 19:00 UTC.
sf_create_custom_objectCreates a new Salesforce Custom Object using the Metadata API. The object name must end with '__c'. Use this when a user asks to create a new object, entity, or table in Salesforce.
sf_create_custom_fieldCreates a new custom field on an existing Salesforce object. The field API name must end with '__c'. Supports all field types: Text, Number, Picklist, Lookup, etc.
sf_add_picklist_valuesAdds new picklist values to an existing Picklist or MultiselectPicklist field without removing existing values. Use when a user wants to add new options to a dropdown.
sf_create_approval_processCreates or updates a Salesforce Approval Process via the Metadata API. Define who can submit, approval steps with approvers, entry criteria, and what happens on approval or rejection.
sf_create_validation_ruleCreates or updates a Salesforce Validation Rule on any object via the Metadata API. The errorConditionFormula returns TRUE when data is INVALID. Use for data quality enforcement.
sf_create_workflow_field_updateCreates a Workflow Field Update action that can be referenced by Approval Processes, Workflow Rules, or Flows. Sets a field to a literal value, formula result, or null.
sf_create_formula_fieldCreates a formula field on any Salesforce object. Supports all return types (Text, Number, Currency, Date, DateTime, Checkbox, Percent) and the full Salesforce formula language: IF/AND/OR/NOT, BLANKVALUE, TEXT, VALUE, DATE, DATEVALUE, TODAY, NOW, date functions (MONTH/YEAR/DAY), math (FLOOR/CEILING/MOD), string functions (LEN/LEFT/RIGHT/MID/TRIM/UPPER/LOWER/CONTAINS/BEGINS), record type and picklist functions (ISPICKVAL, ISNULL, ISBLANK), cross-object field references (e.g. Account.Owner.Name), and VLOOKUP. Complex multi-line formulas are fully supported.
sf_deploy_metadataDeploys a set of metadata components directly to the org using the Metadata API SOAP deploy operation. Builds a package.xml and deployment zip in memory. Supports validate-only (checkOnly:true) for pre-deployment validation without making changes. Specify runTests to execute test classes during deployment (required for production). Polls until complete or timeout.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
SolvScore is categorized under Developer Tools and uses a remote HTTP/SSE transport. Salesforce Metadata MCP belongs to Developer Tools and uses a local stdio subprocess. Pick SolvScore for developer tools work and Salesforce Metadata MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
SolvScore has no declared pricing — check the project's own site. Salesforce Metadata MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add solvscore and salesforce-metadata-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SolvScore has a quality signal of 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Salesforce Metadata MCP has 63/100 (Good) with 2 views, 0 installs and 2 GitHub stars.
sf_check_deploy_statusChecks the status of an in-progress or recently completed metadata deployment by async job ID. Returns the status (Pending, InProgress, Succeeded, Failed, Canceled), component successes, failures, and test results. Use with the deploy ID returned from sf_deploy_metadata.
sf_retrieve_metadataRetrieves metadata components from the org and returns their actual file contents. Use this to read existing configuration before making changes, to back up metadata, or to check what is really deployed rather than what you think is deployed. Waits for the async retrieve to finish and unpacks the resulting zip, returning each file's path and source. Large files are truncated. Accepts 'components' (array), or 'metadataType'+'componentName' as a single-item shortcut, or a raw 'packageXml' document — provide exactly one form.
sf_delete_metadataPermanently deletes one or more metadata components of a given type via the Metadata API's deleteMetadata call — works for CustomObject, CustomField, Flow, GenAiFunction, GenAiPlugin, GenAiPlannerBundle, Bot, ApexClass, and most other metadata types. There was previously no way to remove anything created by this MCP server (sf_deploy_metadata only supports adding/updating components, not destructiveChanges) — diagnostic or abandoned metadata had nowhere to go. Deletes each fullName independently: check the response's deleted/errors lists rather than assuming all all-or-nothing. Some types have dependency order requirements (e.g. delete a Bot's GenAiFunction/GenAiPlugin/GenAiPlannerBundle before the Bot itself, delete CustomField before its parent CustomObject) — Salesforce will reject a delete that still has dependents, naming them in the error.
sf_query_recordsExecutes a SOQL query against the org and returns matching records. Provide the full SOQL string in the query param. Use for reading data, checking existing records before creating, or verifying changes.
Supports aggregate queries — GROUP BY with COUNT(), SUM(), AVG(), MAX(), MIN(), e.g.:
'SELECT StageName, COUNT(Id), SUM(Amount) FROM Opportunity GROUP BY StageName'
Aggregate results come back as regular records with the aggregate expressions as field keys (e.g. "expr0").
Row cap: 'limit' defaults to 200 and is a ceiling, not a hint. If the SOQL carries its own LIMIT the smaller of the two applies, so a LIMIT in the query can tighten the cap but never raise it. When rows are cut off the response sets truncated: true and reports appliedLimit and limitSource, so a capped result is never mistaken for a complete one.
Choose SolvScore when