mcp-registry/io.favcrm/favcrm/list_post_type_fields / alternatives

Live alternatives to mcp-registry/io.favcrm/favcrm/list_post_type_fields

The best live alternatives to mcp-registry/io.favcrm/favcrm/list_post_type_fields right now are mcp-registry/io.simplyprint/simplyprint/list_custom_fields, mcp-registry/io.github.xaviviro/opendata-cat/list_dataset_fields, mcp-registry/io.simplyprint/simplyprint/list_custom_fields_for, mcp-registry/io.github.trackingtime/mcp-server/create_custom_field, mcp-registry/cz.salesbot/linkedin-mcp-server/list_crm_fields — capability-matched and ranked by current reliability. mcp-registry/io.favcrm/favcrm/list_post_type_fields itself is currently "healthy".

alternative	server
mcp-registry/io.simplyprint/simplyprint/list_custom_fields	io.simplyprint/simplyprint	live status →
mcp-registry/io.github.xaviviro/opendata-cat/list_dataset_fields	io.github.xaviviro/opendata-cat	live status →
mcp-registry/io.simplyprint/simplyprint/list_custom_fields_for	io.simplyprint/simplyprint	live status →
mcp-registry/io.github.trackingtime/mcp-server/create_custom_field	io.github.TrackingTime/mcp-server	live status →
mcp-registry/cz.salesbot/linkedin-mcp-server/list_crm_fields	cz.salesbot/linkedin-mcp-server	live status →
mcp-registry/io.poolparty/main-stage-airtime/get_block_type_schema	io.poolparty/main-stage-airtime	live status →
mcp-registry/ar.energetica/data/get_schema	ar.energetica/data	live status →
mcp-registry/com.quintadb/mcp/get_field_types	com.quintadb/mcp	live status →
mcp-registry/ru.quintadb/mcp/get_field_types	ru.quintadb/mcp	live status →
mcp-registry/ua.com.quintadb/mcp/get_field_types	ua.com.quintadb/mcp	live status →
pulsemcp/adbutler/list_data_keys	AdButler	live status →
mcp-registry/com.adbutler/mcp-server/list_data_keys	com.adbutler/mcp-server	live status →

FAQ

What is the best alternative to mcp-registry/io.favcrm/favcrm/list_post_type_fields?

mcp-registry/io.simplyprint/simplyprint/list_custom_fields is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.xaviviro/opendata-cat/list_dataset_fields, mcp-registry/io.simplyprint/simplyprint/list_custom_fields_for, mcp-registry/io.github.trackingtime/mcp-server/create_custom_field, mcp-registry/cz.salesbot/linkedin-mcp-server/list_crm_fields. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.favcrm/favcrm/list_post_type_fields down right now?

mcp-registry/io.favcrm/favcrm/list_post_type_fields's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.favcrm%2Ffavcrm%2Flist_post_type_fields.

How does Glimind pick alternatives?

By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.favcrm%2Ffavcrm%2Flist_post_type_fields or MCP find_alternatives. Check mcp-registry/io.favcrm/favcrm/list_post_type_fields's live status: https://glimind.com/tool/mcp-registry/io.favcrm/favcrm/list_post_type_fields.