io.usefulapi/getfly-crm

None of its 29 tools are described as changing anything. For 29 the reading was uncertain, so no mark is shown.

• getfly_list_users

  “List the Getfly CRM users (employees): user id, name, department, email, phone.”

  Publisher declares: read-only yes · destructive no · open-world yes

  6 inputs

  • sortstring“Field to sort by (e.g.”
  • directionstring“Sort direction, used with sort (default asc).”
  • limitinteger“Records to return, 1-100 (default 20).”
  • offsetinteger“Records to skip (default 0).”
  • fieldsstring“Comma-separated field names to return (e.g.”
  • filtersobject“Filters as { "field": value } or { "field:operator": value }; operators eq, is, in, not_in, contains, between, not_between, gte, gt, lte, lt.”
• getfly_get_user

  “One user by id or by login name (exactly one of user_id and user_username).”

  Publisher declares: read-only yes · destructive no · open-world yes

  3 inputs

  • user_idinteger“User id (from getfly_list_users).”
  • user_usernamestring“User login name.”
  • fieldsstring“Comma-separated field names to return (e.g.”
• getfly_list_accounts

  “List customers (accounts, i.e.”

  Publisher declares: read-only yes · destructive no · open-world yes

  6 inputs

  • sortstring“Field to sort by (e.g.”
  • directionstring“Sort direction, used with sort (default asc).”
  • limitinteger“Records to return, 1-100 (default 20).”
  • offsetinteger“Records to skip (default 0).”
  • fieldsstring“Comma-separated field names to return (e.g.”
  • filtersobject“Filters as { "field": value } or { "field:operator": value }; operators eq, is, in, not_in, contains, between, not_between, gte, gt, lte, lt.”
• getfly_get_account

  “One customer by its customer code (account_code, e.g.”

  Publisher declares: read-only yes · destructive no · open-world yes

  2 inputs, 1 required

  • account_codestringrequired“Customer code (account_code), from getfly_list_accounts.”
  • fieldsstring“Comma-separated field names to return (e.g.”
• getfly_create_account

  “WRITE: Create a new customer (account) in Getfly CRM.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world yes

  20 inputs, 1 required

  • account_namestringrequired“Customer name (company or person).”
  • account_codestring“Unique customer code.”
  • emailstring
  • phone_officestring“Office phone number.”
  • billing_address_streetstring“Street address.”
  • websitestring
  • descriptionstring
  • sic_codestring“Tax code.”
  • birthdaystring“Birthday or founding date, yyyy-mm-dd.”
  • account_manager_usernamestring“Login name of the managing user (getfly_list_users → user_name).”
  • account_type_namesarray“Customer type names.”
  • account_source_namesarray“Customer source names.”
  • industry_namesarray“Industry names.”
  • relation_namestring“Relationship name (e.g.”
  • country_namestring
  • province_namestring
  • district_namestring
  • ward_namestring
  • contactobject“One primary contact person.”
  • custom_fieldsobject“Custom field values by field key.”
• getfly_update_account

  “WRITE: Update fields of an existing customer, found by its current customer code.”

  Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

  17 inputs, 1 required

  • current_account_codestringrequired“The customer's current code (account_code).”
  • account_codestring“New customer code, only to rename the code.”
  • account_namestring
  • emailstring
  • phone_officestring
  • billing_address_streetstring
  • websitestring
  • descriptionstring
  • sic_codestring“Tax code.”
  • birthdaystring“yyyy-mm-dd.”
  • account_manager_usernamestring“Login name of the new managing user.”
  • relation_namestring
  • country_namestring
  • province_namestring
  • district_namestring
  • ward_namestring
  • custom_fieldsobject“Custom field values by field key.”
• getfly_list_campaigns

  “List sales campaigns (opportunity pipelines): campaign code and name, responsible user, lock state, related users and the pipeline stages (status ids and names).”

  Publisher declares: read-only yes · destructive no · open-world yes

  1 input

  • fieldsstring“Comma-separated field names to return (e.g.”
• getfly_get_campaign_stages

  “The pipeline stages of one campaign (status id, name and how many opportunities are in each).”

  Publisher declares: read-only yes · destructive no · open-world yes

  2 inputs

  • campaign_idinteger
  • campaign_codestring
• getfly_list_opportunities

  “List sales opportunities (deals in a campaign pipeline) with code, name, stage, probability, handler, customer and campaign.”

  Publisher declares: read-only yes · destructive no · open-world yes

  7 inputs

  • campaign_codestring“Only opportunities of this campaign (campaign code from getfly_list_campaigns).”
  • sortstring“Field to sort by (e.g.”
  • directionstring“Sort direction, used with sort (default asc).”
  • limitinteger“Records to return, 1-100 (default 20).”
  • offsetinteger“Records to skip (default 0).”
  • fieldsstring“Comma-separated field names to return (e.g.”
  • filtersobject“Filters as { "field": value } or { "field:operator": value }; operators eq, is, in, not_in, contains, between, not_between, gte, gt, lte, lt.”
• getfly_get_opportunity

  “One opportunity by its code (e.g.”

  Publisher declares: read-only yes · destructive no · open-world yes

  2 inputs, 1 required

  • opportunity_codestringrequired“Opportunity code (opportunity_code).”
  • fieldsstring“Comma-separated field names to return (e.g.”
• getfly_list_opportunity_comments

  “The discussion (comments) on an opportunity: author, text and time.”

  Publisher declares: read-only yes · destructive no · open-world yes

  6 inputs, 1 required

  • opportunity_idintegerrequired“Opportunity id (the numeric id, not the code).”
  • sortstring“Field to sort by (e.g.”
  • directionstring“Sort direction, used with sort (default asc).”
  • limitinteger“Records to return, 1-100 (default 20).”
  • offsetinteger“Records to skip (default 0).”
  • fieldsstring“Comma-separated field names to return (e.g.”
• getfly_create_opportunity

  “WRITE: Create a sales opportunity in a campaign for a customer and assign it to a user.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world yes

  9 inputs, 6 required

  • campaign_codestringrequired“Campaign code (getfly_list_campaigns).”
  • account_namestringrequired“Customer name.”
  • account_phonestringrequired“Customer phone number.”
  • contact_namestringrequired“Contact person name.”
  • contact_phonestringrequired“Contact phone number.”
  • recipient_usernamestringrequired“Login name of the user who handles it (getfly_list_users → user_name).”
  • account_codestring“Existing customer code, if the customer already exists.”
  • account_emailstring
  • contact_emailstring

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-03.

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.