io.onesource/mcp

What we checked

Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.

• Injection surface

  fail25% of grade

  Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

  tool "1s_proxy_detect" description: names an outbound copy/exfil destination (BCC/exfil verb).

• Supply chain

  warn25% of grade

  Package provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.

  package name "@one-source/mcp" is edit-distance 2 from popular package "yup" (typosquat candidate)

• Credential hygiene

  fail15% of grade

  How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

  tool "1s_erc1155_balance_live" has a secret-shaped input parameter "token_id" — secrets must never be tool parameters (the model would supply/handle the credential). tool "1s_nft_metadata_live" has a secret-shaped input parameter "token_id" — secrets must never be tool parameters (the model would supply/handle the credential). tool "1s_nft_owner_live" has a secret-shaped input parameter "token_id" — secrets must never be tool parameters (the model would supply/handle the credential).

• Permission scope

  pass15% of grade

  Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

  No shell-exec, unbounded/sensitive filesystem, or download-and-run primitives found in scanned source. PASS = no static red flag. Static scanning is blind to code fetched or executed at runtime.

• Version behavior

  warn10% of grade

  Diff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).

  vs prior 5.10.2 (minor bump): new tool "1s_allowance_live" appeared; new tool "1s_contract_info_live" appeared; new tool "1s_erc1155_balance_live" appeared; new tool "1s_erc20_balance_live" appeared; new tool "1s_erc20_transfers_live" appeared; new tool "1s_erc721_tokens_live" appeared; new tool "1s_events_live" appeared; new tool "1s_multi_balance_live" appeared; new tool "1s_nft_metadata_live" touches a sensitive surface (email/exec/net/fs); new tool "1s_nft_owner_live" appeared; new tool "1s_total_supply_live" appeared; new tool "1s_tx_details_live" appeared; new tool "1s_block_by_number" appeared; new tool "1s_block_number" appeared; new tool "1s_chain_id" appeared; new tool "1s_contract_code" appeared; new tool "1s_ens_resolve" touches a sensitive surface (email/exec/net/fs); new tool "1s_estimate_gas" appeared; new tool "1s_network_info" touches a sensitive surface (email/exec/net/fs); new tool "1s_nonce" appeared; new tool "1s_payment_mode" touches a sensitive surface (email/exec/net/fs); new tool "1s_pending_block" appeared; new tool "1s_proxy_detect" touches a sensitive surface (email/exec/net/fs); new tool "1s_refund" touches a sensitive surface (email/exec/net/fs); new tool "1s_simulate_call" appeared; new tool "1s_storage_read" touches a sensitive surface (email/exec/net/fs); new tool "1s_tx_receipt" appeared; new tool "1s_search_docs" appeared; new tool "1s_get_api_overview" appeared; new tool "1s_list_endpoints" appeared; new tool "1s_get_endpoint_reference" touches a sensitive surface (email/exec/net/fs); new tool "1s_search_use_cases" appeared; new tool "1s_list_networks" appeared; new tool "1s_get_payment_info" appeared; new tool "1s_get_authentication_guide" touches a sensitive surface (email/exec/net/fs); new tool "1s_setup_check" touches a sensitive surface (email/exec/net/fs); new tool "1s_batch_config" touches a sensitive surface (email/exec/net/fs); new tool "1s_report_bug" appeared.

• Transport config

  unscannable10% of grade

  Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

  local stdio server: no remote transport or auth surface, and no phone-home/telemetry signal found in source. Absence of transport findings is NOT a safety guarantee — phone-home hosts can be constructed at runtime and defeat static analysis.