WPReady

The plugin works similar as shortcodes with important differences:
<ul>
<li>It looks for any tag in the post with the following format: {cf your_custom_field_name=your_custom_field_value}</li>
<li>For any tag found, it create a custom field for that post.</li>
<li>The tag is erased from the post.</li>
</ul>
<h4>How to use</h4>
Type in anywhere in a post: 
{cf your_custom_field_name=your_custom_field_value}
Examples:
<ul>
<li>{cf thumbnail=http://wordpressready.com/wp-content/uploads/oneringtorulethemall.jpg}</li>
<li>{cf posticon=/wp-content/uploads/posticon.ico}</li>
<li>{cf my_custom_color=#22fb30}</li>
</ul>
This three examples written inside the post will create three custom fields with respectives values 
when you publish the post. 
After publishing, the tag inside the post are deleted. No other information is erased.
<h4>Notes</h4>
<ul>
<li>Because the way the plugin works, it will run fine with ANY desktop blogger(Windows Live Writer, Scribefire, Qumana, w.Bloggar, Zoundry 
, Thingamablog, Blod Desk, Flock, Post2Blog, Bleezer, you name it)</li>
<li>The plugin can be used even inside the wordpress editor (though what would it be the point?)</li>
<li>You can use any number of custom field for post. </li>
<li>Reserved characters: ‘{cf’ and ‘}’,because it conflicts with the delimiters.</li>
<li>After the post, the tags are automatically erased.</li>
<li>If the custom field is already present, its value will be replaced.</li>
</ul>

Text to Custom Field

Allows adding custom fields from ANY desktop blog editor even if the editor can't support custom fields!

Amin Nazemi

Neatma

Protect your website from xmlrpc brute-force attacks,DOS and DDOS attacks, this plugin disables the XML-RPC and trackbacks-pingbacks on your WordPress website.
PLUGIN FEATURES 
(These are options you can enable or disable each one)
<ul>
<li>Disable access to xmlrpc.php file using .httacess file </li>
<li>Automatically change htaccess file permission to read-only (0444)</li>
<li>Disable X-pingback to minimize CPU usage </li>
<li>Disable selected methods from XML-RPC</li>
<li>Remove pingback-ping link from header</li>
<li>Disable trackbacks and pingbacks to avoid spammers and hackers</li>
<li>Rename XML-RPC slug to whatever you want</li>
<li>Black list IPs for XML-RPC</li>
<li>White list IPs for XML-RPC</li>
<li>Some options to speed-up your wordpress website</li>
<li>Disable JSON REST API</li>
<li>Hide WordPress Version</li>
<li>Disable built-in WordPress file editor</li>
<li>Disable wlw manifest</li>
<li>And some other options</li>
</ul>
What is XMLRPC
XML-RPC, or XML Remote Procedure Call is a protocol which uses XML to encode its calls and HTTP as a transport mechanism. 
Beginning in WordPress 3.5, XML-RPC is enabled by default. Additionally, the option to disable/enable XML-RPC was removed. For various reasons, site owners may wish to disable this functionality. This plugin provides an easy way to do so.
Why you should disable XML-RPC 
Xmlrpc has two main weaknesses
<ul>
<li>Brute force attacks: 
Attackers try to login to WordPress using xmlrpc.php with as many username/password combinations as they can enter. A method within xmlrpc.php allows the attacker to use a single command (system.multicall) to guess hundreds of passwords. Daniel Cid at Sucuri described it well in October 2015: “With only 3 or 4 HTTP requests, the attackers could try thousands of passwords, bypassing security tools that are designed to look and block brute force attempts.”</li>
<li>Denial of Service Attacks via Pingback: 
Back in 2013, attackers sent Pingback requests through xmlrpc.php of approximately 2500 WordPress sites to “herd (these sites) into a voluntary botnet,” according to Gur Schatz at Incapsula. “This gives any attacker a virtually limitless set of IP addresses to Distribute a Denial of Service attack across a network of over 100 million WordPress sites, without having to compromise them.”</li>
</ul>

Disable XML-RPC-API

The upgrade notice keeps coming back on every screen even after being dismissed. It looks very unprofessional to my clients and is embarrassing for me as a web developer, i would rather disable the plugin and use the code in a function. 

It should be permanently dismissible via a cookie, like for other plugins. It might be ok once, when the plugin is first installed or updated, but after that, it should never appear again. 

Good plugin, but upgrade nag is too annoying

A simple and lightweight plugin to disable XML-RPC API, X-Pingback and pingback-ping in WordPress 3.5+ for a faster and more secure website

Text to Custom Field vs Disable XML-RPC-API